Creating a Screen Flow with a Server-Initiated Starting Point

Use the Hybrid App Designer wizard to define a screen flow with a starting point that is activated when a notification message is sent to a device identified by matching rules in the Hybrid App.

1. In the Mobile Development perspective, select File > New > Hybrid App Designer.
2. Follow the instructions in the Hybrid App Designer wizard:
   • Enter or select the parent folder – select the Hybrid App project in which to create the Hybrid App screen flow.
   • File name – enter a name for the Hybrid App screen flow. The extension for Hybrid App screen flows is .xbw.
   • Advanced – link the Hybrid App screen flow to an existing file in the file system.
   • Link to file in the file system – click Browse to locate the file to which to link the Hybrid App screen flow. Linked resources are files or folders that are stored in the file system outside of the project's location. If you link a resource to an editor, when you select the editor, the resource is selected in the WorkSpace Navigator. Conversely, when you select the resource in the WorkSpace Navigator, the editor is selected.

     Click Variables to define a new path variable. Path variables specify locations on the file system.

3. Click Next.
4. In the Starting Points page, select Responds to server-driven notifications and click Next.
5. In the Select a Mobile Business Object and Object Query page, click Search.
6. In the Search for Mobile Business Object page:
   1. Click Search.
   2. Accept the current project or choose a different one.
   3. Click Search.
   4. Select a Mobile Application Project from the list and click OK.
7. (Optional) In the Select a Mobile Business Object and Object Query page, select an object query and click Next.
   • Consider using an object query if you want the Hybrid App message to use data from the back end or from the SAP Mobile Platform cache that is not available in the originating notification.

     In this scenario, you can use extraction rules to get input parameters for the object query from the originating notification. Then, you can get the data values for the workflow message from the query result set.

   • You do not need an object query if all of the data values for the workflow message are available in the originating notification. In this scenario, you can use extraction rules to obtain the data values directly from the originating notification.

   Note: Object queries that return result sets are not supported.
8. In the Specify Sample Notification page, enter contents in the fields that you want to appear in the sample notification message, then click Next.
   For example enter Order (2001) created as the Subject.
9. In the Specify Matching Rules page:
   1. Select the text that will serve as the matching rule.
   2. Right-click and select Select as Matching Rule to create the matching rule.
   3. Click Next.
10. In the Identify Parameter Values page, select an extraction rule and specify its properties.
    Note: The supported syntax for regular expressions is that used by the C# Match() methods of the class System.Text.RegularExpressions.Regex.

    • Field – select the field from the notification message from which the parameter receives data, for example, Subject. Selecting Subject indicates that the parameter receives data from the subject line of the notification message.
    • Start tag – enter or select the text for the start tag regular expression, for example, "Approval Request\(".
    • End tag – enter or select the text for the end tag regular expression, for example, "\)was sent".
    • Format – specify a format that supports locale-specific parameter extraction. For example, you can indicate that a given date parameter will be in the form of yyyy-MM-dd in the e-mail, and another date parameter will be in the form of yyyy-dd-MM. This applies to the DateTime type.
    • Sample notification field contents – enter the value of the field previously specified on the Specify Sample Notification page of the Notification Processing wizard.
    • Value extracted from sample notification field contents – specify the value the start tag and end tag matching rules, given the sample field value.
11. Click Finish to create default screens and starting points.
    When the notification is sent to the client, the sample value is replaced with the specified key, and the client's form is populated with values returned by the object query

• Notification Extraction Rules
  Notification extractions rules are used to extract parameter values to keys, so you can then map the parameters to objects, such as keys.