Scenario

In this activity, you will take the existing XML-processing rule set and change the way it gets its intent. In the existing rule set, when an XML file is dropped into a job hot folder, RBA then processes that intent in various actions along a chain.

In this new scenario, RBA will get that same intent via a different method. The basic structure and performance of the rule set remains the same, but the way it gets the XML file is different.

In one job, you will create a 'sender' rule set that will be configured to call a 'receiver' rule set in another job. The sender will provide a path to the XML file that the receiver will consume via its Send Remote Trigger action.

So, when you run the sender rule set, it will call the receiver and pass it the appropriate values (via parameter values and strings). The receiver will then act on those event values. The receiver rule set is exactly the same as the one you created in activities 1-12, except that instead of a hot folder drop trigger event, it will start with a remote trigger event.

In this activity, you will work with four different jobs:

• <XX>_RBA_Job – This is where the XML file Self-Study.xml is stored.
• <XX>_Remote_Job – This is the resulting job of the XML workflow.
• <XX>_Hub_Job – This is where <XX>_Rule_Set_XML_Remote_Sender is enabled.
• <XX>_Spoke_Job – This is where <XX>_Rule_Set_XML_Remote_Receiver is enabled.

Important: Please note that RBA requires precision in the names of jobs and rule sets. If there are spelling mistakes in any of these names, for example, if an underscore is missing, the rule set will not work. Please pay close attention to the spelling of the jobs and rule sets in this activity.