Upload mWorkOrder RACE™ pre-set Configuration Spreadsheets

mWorkOrder configuration RACE Spreadsheets

• Admin Configurations: (Mandatory file) Upload this file during the product deployment. You cannot reconfigure the settings.
• Applications: (Mandatory file) Upload this file during the product deployment and reconfigure as required later.
• Defaults: (Recommended file) Upload this file during the product deployment. The configurations in the file ensure that the application works as designed. However, you can reconfigure as required later.
  Note:

  • If UI field type is related to drop down, check and maintain dynamic drop-down configuration fields data properly (DD TABLE NAME, DD FIELD NAME, TEXT REQ, TEXT TABLE NAME, TEXT FIELD NAME, TEXT KEY FIELD NAME, DEPENDENCY FIELD NAME, DEPENDENCY KEY FIELD NAME).
  • Try to avoid Transaction tables in DD Table Name (MARA, VBAK, MARC, MSEG).
  • Dynamic drop-down table should have very less data (< 1000 entries). If we have more data in dynamic drop-down table, there will be chances of offline store failure.
• Dynamic Search: (Recommended file) Upload this file during the product deployment. The configurations in the file ensure that the application works as designed. However, you can reconfigure as required later.
  Note:

  • At least one search field should be active for each module name and search screen name.
  • If UI field type is related to drop down, check and maintain dynamic drop-down configuration fields data properly (DD TABLE NAME, DD FIELD NAME, TEXT REQ, TEXT TABLE NAME, TEXT FIELD NAME, TEXT KEY FIELD NAME, DEPENDENCY FIELD NAME, DEPENDENCY KEY FIELD NAME).
  • Try to avoid Transaction tables in DD Table Name (MARA, VBAK, MARC, MSEG). Dynamic drop-down table should have very less data (< 1000 entries).
  • If we have more data in dynamic drop-down table, there will be chances of offline store failure.
• Dynamic Screens: (Reference file) Use this file as a reference to configure additional screens (custom tabs or forms) in any module as required and upload it.
• Extensions: (Reference file) Use this file as a reference to create similar kinds of configurations based on your requirements and upload it.
  Note:

  • If UI field type is related to drop down, check and maintain dynamic drop-down configuration fields data properly (DD TABLE NAME, DD FIELD NAME, TEXT REQ, TEXT TABLE NAME, TEXT FIELD NAME, TEXT KEY FIELD NAME, DEPENDENCY FIELD NAME, DEPENDENCY KEY FIELD NAME).
  • Try to avoid Transaction tables in DD Table Name (MARA, VBAK, MARC, MSEG).
  • Dynamic drop-down table should have very less data (< 1000 entries). If we have more data in dynamic drop-down table, there will be chances of offline store failure.
• Filters: (Recommended file) Upload this file during the product deployment. The configurations in the file ensure that the application works as designed. However, you can reconfigure as required later.
  Note:

  • Try to filter the data as much as the end user requires.
  • Do not maintain any junk data.
• Modules and Screens: (Mandatory file) Upload this file during the product deployment and reconfigure as required later.
• Operator Rounds: (Mandatory files) Upload the following files to use operator rounds feature during product deployment and reconfigure later.
  • Operator Rounds - Attachment type
  • Operator Rounds - Attributes
  • Operator Rounds - Extensions
  • Operator Rounds - Frequency
  • Operator Rounds - Schedule
  • Operator Rounds - Shift
  • Operator Rounds - UI Control Type
• Performance: (Mandatory file) Upload this file during the product deployment and reconfigure as required later. The configurations in the file ensure that the performance of application is optimized.
  Note:

  • Sync the collections to offline as per the customer scope only.
  • For drop-down collection, if no. of entries < 1000, then enable delta token and offline sync. Access from offline should be active.
  • For drop-down collection, if no. of entries > 1000, then enable skip token and offline sync. Skip token size should be 500 to 1000. Access from offline should be active.
  • For expand collections, enable skip token and offline sync. Access from offline should be active.
  • Delete any duplicate collections.
  • If expand collection (WORKORDERHEADERCOLLECTION?$expand=operationscollection...etc.) is enabled for offline sync, then there is no need to enable the offline sync for plain collection (GROPHEADERCOLLECTION). We maintain expand collection and plain collection separately only to increase the skip token value in online mode.
• Scoping: (Mandatory file) Upload this file during the product deployment and reconfigure as required later.
  Note:

  • Each entry should have a system name.
  • Do not configure any static feature directly in customer environment. It should come through P&I.
  • Do not maintain any junk data.
• UILabelCollection: (Mandatory file) Upload this file during the product deployment and reconfigure as required later
• Dynamic Forms: (Reference file) Use this file as a reference to create similar kinds of configurations based on your requirements and upload it.
• Push Notifications: (Reference file) Use this file as a reference to create similar kinds of configurations based on your requirements and upload it.
• Risk Matrix: (Reference file) Use this file as a reference to create similar kinds of configurations based on your requirements and upload it.