• SBM should offer a scheduler to start and execute processes or batches of processes. A process is defined as any of the following:    appScript    Orchestration    import definition set in SBM System ...admin import tool     Other misc data process SBM should support a scheduler to start and execute processes or batches of processes. A process is defined as any of the following:    appScript    Orchestration    import definition set in SBM System admin import tool     Other misc data process    A batch and a process should support the following parameters    Start time    reoccurring execution interval     length of time that audit history should be maintained    name    type (script, orch, import definition set, CopyValueFromFieldToAnotherField, CopyThisValueToThisField, DeleteRecords, ExecuteCommand)    Execution order - for processes that are included in a batch    Log Level (error, info, debug)    ActiveInactive    The parameters for each type will vary. For example,     CopyValueFromFieldToAnotherField : Name, Table, where clause, Source Field, Destination Field         CopyThisValueToThisField  : Name, Table, where clause, Value, Destination Field             DeleteRecords  : Name, Table, where clause     ExecuteCommand  : Name, Command Line, Command line parameter     The activities that the scheduler performs should be audited with the following details:    start time    time completed    total execution time    Result Summary of execution     Currently Running    The definition of scheduled processes should be creatable via the web interface. Individual processes should also offer the ability to allow the user to run the process immediately. Process and batches should be allowed to be set to inactive so they are not executed by the scheduler yet they remain in place so that they can be enabled at a later date. All Processes and batches should be promotable via the application repository manager. I have produced this type of system for multiple clients over the past 10 years. More

Recent Tweets