Handling manual intervention

Help Orchestrator
, ,
1

We have two requirements as below:

  1. Trigger process at next day (Wed) of 2nd tuesday of month.
  2. Check and validate in every 30 minutes whether email arrived on next day (Thur) during 3 am to 5 am.
    If email is received then it is okay else notify alerts to team about no email is sent by them.

—‐--------

  1. Objective is to trigger process at next day (Wednesday) of 2nd tuesday of month.

Proposal : Process is scheduled at 2nd tuesday of month at 4 am and create transaction item with postponed period: add(1) day with time and add to orchestrator queue.

  1. Another requirement is to check and validate every 30 mins whether an email is received with specific subject b/w 3 am-5 am.

Proposal : Above process will also create additional 4 transactions to trigger sub process(to check and validate emails) : create transaction items with postponed period add(2) day between 3-5am. and trigger process to check and validate emails in that time window.

Only problem with this approach is to trigger sub process after postponed period date time and mark transaction status : “Failed” for no emails received and “Success” for email received (Which will be only one scenario).

2

@Sonalk

Ideally if queue based trigger is enabled then once the queue item is available the bot would trigger automatically

cheers

1 Like
3

Hi @Sonalk,

Your proposed approach seems feasible for triggering the process at the next day of the 2nd Tuesday of the month and for checking and validating emails every 30 minutes between 3 am to 5 am.

To address the issue of triggering the sub-process after the postponed period and marking the transaction status, you can use the following steps:

  1. Create a separate workflow for the sub-process that checks and validates the emails.
  2. When creating the transaction items for the sub-process, set the postpone period to add(2) day between 3-5am, as you have proposed.
  3. In the sub-process workflow, use the “Get Transaction Item” activity to retrieve the transaction item.
  4. Use the “Get Outlook Mail Messages” activity to check for the specific email subject.
  5. If the email is received, mark the transaction status as “Success” using the “Set Transaction Status” activity.
  6. If the email is not received, mark the transaction status as “Failed” using the “Set Transaction Status” activity.
  7. Use the “Delay” activity to wait for 30 minutes before checking for the email again.
  8. After the delay, repeat steps 3 to 7 until the end of the postponed period.

By using this approach, you can ensure that the sub-process is triggered after the postponed period and that the transaction status is marked correctly based on whether the email is received or not.

4

@ABHIMANYU_THITE1 : Thanks for sharing the details.

Step 7 —>The only limitation of this approach is to restrict one robot for 2 hours job execution and checking emails in every 30 minutes.

Efficient method → No email is yet received : Is there a way to change current transaction status “In Progress” to “New” with next postponed period (next 30 minutes) so that same process will get triggered again.

1 Like