Configure Business Rules, Workflow and Process Visibility

The sample business rule used in this scenario is published in API Business Hub. BUSINESSRULES_APIHUB destination is used in Manage Rule Projects application to import business rules from API Business Hub. This destination is already created in the previous set up tutorial, and now you will configure the destination for the password.

1. From your global account page, choose the trial tile to access your subaccount.

   

2. Click Connectivity | Destinations from the left-hand navigation and search for the destination with name BUSINESSRULES_APIHUB

   

3. In Destination Configuration section, click Edit and enter your cloud platform trial user password:

   Ensure that the user whose credentials (username and password) are entered in the destination does not have Two Factor Authentication enabled.

   
   • Save the destination.

To import the business rules project from API Business Hub, you need to configure a system which points to the API Hub destination and then use this system to import the project.

1. In your web browser, open the Workflow Management application and click the Manage Rule Projects tile..

   You got the workflow management application link in the last step of the set up tutorial. The link would be like:

   https://<subdomain>.cockpit.workflowmanagement.cfapps.<eu10 or us10>.hana.ondemand.com/cp.portal/site#Shell-home

   

2. Open Configure Systems.

3. Click + to add a system.

   

4. Enter the following details:

   Field Name	Value
   Name	APIHub
   Destination	BUSINESSRULES_APIHUB or the name of the destination you created in the set up tutorial

5. Save the system configuration.

   

1. Click Design icon, click Import to select Import Project from API Business Hub.

   

2. In the popup, do the following:

   • In the System field, select APIHub or the name you entered while configuring the system.
   • From the options shown in the Content Package Name dropdown, choose Equipment Determination Business Rules.
   • Choose Go.
   • Select the latest version of the project named Equipment Determination Rules.
   • Choose Import.
   

   If you get Bad Gateway Error error, then check the username and password you have used in BUSINESSRULES_APIHUB destination. If your user is 2-Factor-Authentication enabled, then the password will be password+passcode. This passcode will expire in a minute.
   If you do not have 2-Factor-Authentication enabled and still get this error, then check if you are member of SAP API Business Hub. Log in to api.sap.com and try importing again.

3. You will see the business rules project imported and in Active status.

   

1. Select the business rules project to navigate into the project.

   

2. Switch to the Rule Services tab.

3. Click Deploy to deploy rule services DetermineEquipmentRuleservice and EquipmentApprovalRuleservice.

   

4. Select the Cloud Runtime option.

   

5. Wait for the deployment to complete. You will get a popup message once the deployment is successful.

Only deployed business rules can be consumed via APIs published in API Business Hub.

1. Download cf-onboarding-sample.zip project from GitHub in your local file system and extract the files.

   

2. Open SAP BTP Trial Homepage and choose SAP Business Application Studio.

   

   If you get the privacy statement screen, then click Ok to accept it.

3. Click on the Dev Space to go into the workspace and from File menu choose Open Workspace

   • If you do not have any dev-space, then click Create Dev Space. In the New Dev Space page, enter any dev space name, select SAP Fiori kind and Workflow Management extension. Finally click Create Dev Space to create a space in your business application studio.
     

     

   • If you have a dev-space but Workflow Management extension is not added then click on Edit button, select Workflow Management and Save Changes.
     

     
     
     
     

   • If you have the dev-space with Workflow Management extension added, and the dev-space status is STOPPED then click on the run button to start the space.
     

     

   

   Some File menu options might not appear as they are not relevant if you are opening the workspace for the first time without any projects.

4. Drag and drop the extracted cf-onboarding-sample project in the dialog and click Open.

   
   

5. You will see that the cf-onboarding-sample project is imported into your workspace.

   

   This sample workflow has:

   • Business Rules integrated into it. You can find the integration as part of service task with name Determine Equipment.

   • User Tasks for confirmation of the equipment selected via business rules and for the approval of equipment. You can find these user tasks with the names Confirm and Change Equipment, Approve Equipment and Accept Workplace respectively. The user interface associated with these user tasks has been built using Workflow Form and you can find these under forms folder in the same multi target application.

1. Right-click the mta.yml file inside the cf-onboarding-sample project, and choose the Build MTA option.

   

2. Once the build is completed successfully, right-click on the mta_archives | sample-onboarding.mta_0.0.1.mtar file and choose Deploy MTA Archives.

   

   The deployment will fail if you have not logged in to the trial account. Click Function F1 to open the login wizard and follow the wizard to log in to your trial account.
   

   

   A successful deployment message will be shown in the terminal once the deployment has completed successfully.
   

   

1. In your web browser, open the Workflow Management application and choose Configure Visibility Scenarios.

   You should have gotten the workflow management application link in the last step of the set up tutorial. The link should be like this:

   https://<subdomain>.cockpit.workflowmanagement.cfapps.<eu10 or us10>.hana.ondemand.com/cp.portal/site#Shell-home

   

2. To create a new visibility scenario, choose +.

   

3. Enter Name as Employee Onboarding, any Description of your choice, and click Create.

   

   The business scenario will be created with Draft status.

   

1. Navigate into the newly created scenario and click the Processes tab, choose + and select Add Workflow to add workflow to business scenario.

   

2. Select the onboard workflow from the choices.

   

   onboard is the sample workflow that you have deployed in the previous tutorial.

3. The workflow is added and all the needed Events and Context are imported as well.

   

1. Switch to the General tab.

2. In the Instances Label field, enter Onboardings and in the Instance Label field enter Onboarding.

   

3. Switch to the Status tab.

4. In the Sub-Status section, select At Risk and choose +.

   

5. In the Name field for the risk status, enter Approval Pending or anything of your choice and click Ok.

   

6. In the properties, enter the following:

   Field Name	Value
   Expression Type	Event A occurred and not Event B
   Event A	Approve Equipment Created
   Event B	Approve Equipment Completed

   

To activate the business scenario, choose Activate.

Activate operation saves and activates the scenario. Only an activated business scenario can be consumed.