Scheduled Jobs
A job scheduler is a program that enables an enterprise to schedule and, in some cases, monitor computer "batch" jobs (units of work, such as the running of a payroll program). A job scheduler can initiate and manage jobs automatically by processing prepared job control language statements or through equivalent interaction with a human operator. The jobs created for this solution are:
- FTOS_IB_AcquireAndUpdatePymtStatus
-
FTOS_IB_BulkPaymentsListJobs
- FTOS_IB_CreateAnonymizationRequests
- FTOS_IB_GetParticipantBankSchema
- FTOS_IB_PaymentsQueue
- FTOS_IB_RetryEasyPayRequests
- FTOS_IB_SyncCountries
- FTOS_IB_Utility_EasyPay
- FTOS_IB_UtilityReverseBill.
These jobs have to be created manually during the installation process within Innovation Studio by a system user with administrative security role associated.
- From the Innovation Studio main menu, click Automation Blocks > Scheduled Jobs. The Scheduled Jobs List page is displayed.
- At the top right-hand corner of the page, click the Insert icon. The Add Scheduled Job page is displayed.
- Add the following jobs as they are defined here.
After they are created, one field can be modified Cron Expression on the page Edit scheduled job or you can click Run Now to initiate the job execution.
FTOS_IB_AcquireAndUpdatePymtStatus
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_AcquireAndUpdatePymtStatus. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Select from the list:
Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute.
Cron Expression Text 0 0 * * * At 12:00 AM Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to NULL.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_AcquireAndUpdatePymtStatus, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_AcquireAndUpdatePymtStatus |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_AcquireAndUpdatePymtStatus |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_BulkPaymentsListJobs
- runs every 5 min
- calls FTOS_IB_BulkPaymentsListJob server automation script using the customer flow FTOS_IB_BulkPaymentsList
-
runs the job for all bulk payments with status
Not Rejectedand withcoreBankingMassIdnot null andcoreBankingValidationIdnot null. - retrieves the updated business status according to the mapping of the statuses in the API (
Sent,Successful,Rejected Core) - after one day in status registered the bulk file is considered
Rejected.
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_BulkPaymentsListJobs. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Select from the list:
Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute.
Cron Expression Text 0 0/5 * 1/1 * ? * Every 5 minutes Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to TRUE.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_BulkPaymentsListJobs, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_BulkPaymentsListJobs |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_BulkPaymentsListJobs |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_CreateAnonymizationRequests
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_CreateAnonymizationRequests. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Select from the list:
Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute.
Cron Expression Text 0 0 0 31 12 ? At 12:00 AM, on day 31 of the month, only in December Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to NULL.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_CreateAnonymizationRequests, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_CreateAnonymizationRequests |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_CreateAnonymizationRequests |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
TRUE NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_GetParticipantBankSchema
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_GetParticipantBankSchema. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Select from the list:
Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute.
Cron Expression Text 0 0/60 0 1/1 * ? * Every 60 minutes, between 12:00 AM and 12:59 AM Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to NULL.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_GetParticipantBankSchema, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_GetParticipantBankSchema |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_GetParticipantBankSchema |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_PaymentsQueue
This Scheduled Job runs every minute to see the payments with the status Authorized, which are NOT Local Currency Instant or SEPA Instant, and tries to process them in Core Banking.
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_PaymentsQueue. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute. Cron Expression Text 0 0/1 * 1/1 * ? * Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to TRUE.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_AcquireAndUpdatePymtStatus, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_PaymentsQueue |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_PaymentsQueue |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_RetryEasyPayRequests
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_RetryEasyPayRequests. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Select from the list:
Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute.
Cron Expression Text 0 0/1 * 1/1 * ? * Every minute Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to NULL.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_RetryEasyPayRequests, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_RetryRequestEasyPay |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_RetryRequestEasyPay |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_SyncCountries
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_SyncCountries. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Reschedule After Run Boolean NULL Scheduled Type Option set Pool Time. It refers to the number of threads that can be pooled at once by the underlying Thread Pool Executor the notional number of methods that can be run at the same time. Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to TRUE.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_SyncCountries, there is the following service:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_SyncCountries |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_SyncCountries |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
TRUE NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
|
Field |
Data Type |
Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_Utility_EasyPay
This job updates the list of providers and it checks automatically at the beginning of the day the amount.
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_Utility_EasyPay. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute. Cron Expression Text Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to NULL.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to NULL.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
For FTOS_IB_Utility_EasyPay, there is the following services:
FTOS_IB_EasyPay_GetServicesAndProviersList:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_EasyPay_GetServicesAndProviersList |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_EasyPay_GetServicesAndProviersList |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
FTOS_IB_EasyPay_CheckContracts:
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_EasyPay_CheckContracts |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_EasyPay_CheckContracts |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.
FTOS_IB_UtilityReverseBill
1 Parameters
- Open the Innovation Studio using the credentials given for login.
- From the main menu, click Fintech Automation, the child menu Scheduled Jobs.
- The Scheduled Jobs List is displayed. From the list, select FTOS_IB_UtilityReverseBill. The page Edit scheduled job is displayed.
- The following fields have the configurations:
Field Data Type Description Name Text It is the name of the job. Start Time Date It is the time when the job started running. End Time Date It is the time when the job was completed. Scheduled Type Option set Cron Expression. Cron runs as a daemon process. This means it only needs to be started once and it will keep running in the background. This process makes use of crontab to read the entries of the schedules and kicks off the tasks. Each line in cron is an entry with an expression and a command to run. This entry runs the mentioned script every single minute. Cron expression Text 0 0/1 * 1/1 * ? * Every minute Calendar (exclude days) JSON It is the execution calendar for the job. Send Notification Boolean If true, then the job sends notifications.
It is set to TRUE.
Send Notification On Error Boolean If true, then the job sends notifications related to execution errors.
It is set to NULL.
Enabled Boolean If true, the job is active. If false, the job is deactivated.
It is set to TRUE.
2 Schedule Services
This grid displays the existing services for the current job. Parameterizing a scheduled service means assigning an workflow that must be executed (run) by the job either synchronously or asynchronously.
| Field | Data Type | Description | Example |
|---|---|---|---|
| Name | Text | the name of scheduled service on the current scheduled job | FTOS_IB_RetryReverseBill |
| Workflow | Lookup | select from the list the workflow that you want this service to run on this scheduled job | FTOS_IB_RetryReverseBill |
| Async | Boolean | execution type – asynchronous or synchronous | NULL |
| Mandatory | Boolean | this service to be mandatory in the current job. |
NULL NOTE
You can mention here if you want this service to be mandatory in the current job, if applicable. |
3 Execution History
In the Scheduled Job section tab, a user sees the execution history of the currently selected job. This history is constantly updated in the event that a new execution is scheduled or manually triggered by the operator using the Run option.
By selecting a past instance, a user can re-configure a scheduled job (from history) to run again. To re-configure a selected job from the execution history it is necessary to complete or modify the following parameters:
| Field | Data Type | Description |
|---|---|---|
| Name | Text | It is the name of the instance/execution. |
| Start Time | Date | It is the start date of the execution. |
| End Time | Date | It is the end of the execution. |
| Scheduled Type | Option set | It is the type of job: Cron Expression or Pool Time |
| Repeat Count | Whole number | It is the number of executions done. |
| Reschedule After Run | Boolean | It is the re-programmed execution after a time interval. |
| Cron Expression | Text | It is the Cron expression. |
| Calendar (exclude days) | JSON | It is the execution calendar. |
| Send Notification | Boolean | It marks if the execution sent notifications. |
| Send Notification On Error | Boolean | It marks if the execution sent notifications related to execution errors. |
| Enabled | Boolean | It marks if the execution was active of inactive. |
4 Monitoring scheduled jobs and their executions
FintechOS provides the job control functionality defined on the platform.
The user with the role of monitoring the platform and the solutions can access this Control Panel which provides the following functionalities:
- Creating and managing new date regarding the execution of jobs.
- Manual execution control: The user can start the execution by selecting the RUN option.
- View the execution history for the selected scheduled job.
Manual execution control: The user can start the execution by selecting the Run Job option.
View the execution history for the selected scheduled job.