Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Mobile Operator

Best practices for configuring Work Order templates

Best practices for configuring Work Order templates

  • Last UpdatedFeb 19, 2025
  • 1 minute read
  • All items, such as Work Order Templates and Response Lists, should be used within a given hierarchy. They should not be cross referenced across plants or organizations in a different hierarchy.

  • Work Order Request Templates should only be linked to a Plant (organization of type 2)

  • Response lists can be imported into an Organization or Plant (organization of type 1 or 2)

  • Assets can be imported to a Plant only (organization of type 2)

  • The name of a Response List should be unique within an Organization, Application ID, and hierarchy.

  • The Application ID and Application Item ID should be unique for an Asset or Response List in the database.

  • To ensure consistency with using Search and Sort in the mobile app Work Order Requests Listing, the following should be configured the same across all templates:

    • Search is enabled only if the Short Text field is set in the ShowInBrowser field of the SAT_WRS_FIELD_SETUP_MOBILE table in the Database.

    • Sort parameters include the fields set in the ShowInBrowser field of the SAT_WRS_FIELD_SETUP_MOBILE table in the AVEVA Mobile Operator database .

TitleResults for “How to create a CRG?”Also Available in