Understanding when rule support in offline mode

Offline-enabled mobile apps support when rules to a certain extent. By learning how when rules work in offline-enabled mobile apps, you can ensure that your offline-enabled mobile app operates reliably.

Pega Platform packages the when rules that you apply in supported use cases for offline-enabled mobile apps into the mobile app distributable files. When you design a when rule and use a feature that is not supported, offline-enabled mobile apps do not process rules with unsupported features, and add error messages to the log files.
Note: Validation of when rules happens at run time. To review the errors, you can request logs from a device. For more information, see Retrieving device logs.

Supported use cases

You can reference when rules in the following contexts in offline-enabled mobile apps:

  • Decision shape flow actions
  • Question shape flow actions
  • Field validation
  • Conditional starting and skipping of a process
  • Visibility and disable conditions for controls, with the exception of the navigation rule
Note: Offline-enabled mobile apps also support flows with multiple connectors with a when rule, connected to either a decision or question shape of a fork type. If two or more connectors can simultaneously evaluate to true, you must assign a different likelihood to such connectors.

Supported features

Offline-enabled mobile apps support the following features that you can use when you design the logic of the when rule:

  • Conditions:
    • [first value] [relation] [second value]
    • [first string] equals [second string]
    • [first string] does not equal [second string]
    • [string to search on] contains [string to search for]
    • [first String] [relation] [Second String]
    • [first number] [relation] [second number]
    • [First DateTime] [relation] [Second DateTime]
    • [a datetime] is in the [past/future]
    • created within the last [num] days
    • the work object is Resolved
    • the work object's status is [given value]
    • the customer satisfaction status is [given value]
    • [Pagelist Name] contains a page where [Property Name] equals [Value]
    • length of [a pagelist property] is [comparison operator] value
    • [expression evaluates to true]
    • rule [When record evaluates] to true
  • Single-value properties on the following system pages:
    • Data-Admin-Operator-AccessGroup for AccessGroup
    • Data-Admin-Operator-ID for OperatorID
    • Data-Admin-Organization for Org
    • Data-Admin-OrgDivision for OrgDivision
    • Code-Pega-Process for pxProcess
    • Code-Pega-Thread for pxThread
    • Code-Pega-Requestor for pxRequestor
    • Rule-Application for Application
  • All utility functions and libraries that are supported in offline mode. For more information, see Understanding function rule support in offline mode.
  • Nested when rules in the expression that you build with the following functions for the [expression evaluates to true] condition:
    • when
    • callWhen
      Note: The the callWhen function has limited offline support for when rules. For more information, see the following paragraph.

Consider the following information with regard to when rule support by the callWhen function:

  • The third parameter must be myStepPage or pyWorkPage. For example, offline-enabled mobile apps support the following code: 
    @callWhen(@getPublicAPI(),"AtCallWhenInner",pyWorkPage)
  • You cannot dynamically call a when rule by using a text reference. For example, offline-enabled mobile apps do not support the following code: 
    @callWhen(@getPublicAPI(), .MyTextProperty, myStepPage)

Unsupported features

Offline-enabled mobile apps do not support the following features that are related to the logic of when rules:
  • Conditional routing
  • Case-wide validation
  • When rules that reference a section parameter page
  • Visibility conditions for layouts
  • Required conditions