{"id":28639,"date":"2024-04-01T06:39:29","date_gmt":"2024-04-01T06:39:29","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=28639"},"modified":"2024-12-03T05:12:24","modified_gmt":"2024-12-03T05:12:24","slug":"how-to-update-the-fields-in-the-signature-history-table-for-a-custom-workflow","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2024\/04\/01\/how-to-update-the-fields-in-the-signature-history-table-for-a-custom-workflow\/","title":{"rendered":"How to Update the Fields in the Signature History Table for a Custom Workflow"},"content":{"rendered":"\n

In Sage X3, workflows are used to automate and streamline business processes by defining a sequence of tasks that need to be performed in a specific order. These tasks can involve approvals, reviews, or other actions necessary for the completion of a business process. Workflows in Sage X3 help organizations enforce consistency, reduce manual intervention, and improve efficiency.<\/p>\n\n\n\n

In Sage X3<\/a>, you can assign multiple signatures in a workflow on different objects to implement a multi-level approval process. This allows for more complex and controlled workflows, where different users or groups need to review and approve various stages of a business process. But when we create the custom workflow the signature history is not getting the proper flow, and the flags are not updated.<\/p>\n\n\n\n

Here’s a step-by-step description of how to update the fields in the signature history table for a custom workflow in Sage X3:<\/p>\n\n\n\n

STEP 1: <\/strong><\/p>\n\n\n\n

Workflow Setup:\u00a0<\/strong> First, you need to define the workflow itself. Go to the –>>”Workflow Setup” screen in Sage X3,\u00a0 where you can create and configure the workflow according to your business requirements.<\/p>\n\n\n\n

Specify the objects for which you want to implement the workflow, such as purchase orders, sales orders, or expense reports.<\/p>\n\n\n\n

STEP2:<\/strong><\/p>\n\n\n\n

After clicking on workflow rules,<\/p>\n\n\n\n

Jump to: Assignment Rule: Create a New Assignment Rule<\/strong><\/p>\n\n\n\n

Signature Assignment: <\/strong>Once you have defined the signature levels, you can assign the relevant users or user groups to each level. This is done based on the roles and responsibilities of the users in your organization. Sage X3 allows you to easily select the appropriate users or groups from your system’s user database<\/p>\n\n\n\n

STEP 3:<\/strong><\/p>\n\n\n\n

-After clicking on the Assignment Rule display below the<\/p>\n\n\n\n

-Enter the name of the assignment rule, the data model, and Number of ignatures.<\/p>\n\n\n\n

-The “number of signatures” field specifies how many signatures will be used throughout the approval process.<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

Fig 1. Assignment Rules <\/strong><\/p>\n\n\n\n

STEP 4:<\/strong><\/p>\n\n\n\n

After all the creation processes Save and validate the assignment rule and workflow rule.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

                                                Fig 2. Signature History<\/strong><\/p>\n\n\n\n

STEP 5:<\/strong><\/p>\n\n\n\n

After completing all the creation processes and successfully triggering the workflow to the next user, such as ‘TEST2,’ we observed in the signature history, as shown in Figure 4, that the signed flag was updated to ‘To sign.’ However, when the user modified the order and saved it, the workflow was triggered again with the updated order, and the signed flag was updated to ‘Cancelled,’ and the reason flag was updated to ‘Document modified.’ However, for the custom workflow, the signatures history table is not updated automatically, as is the case with the standard workflow. Therefore, we need to manually update the flag in the table.<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

   Fig 3. Store requisition <\/strong><\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

                                                Fig 4. Signature History<\/strong><\/p>\n\n\n\n

STEP 6: <\/strong><\/p>\n\n\n\n

The signature history data is stored in the ‘AWRKPARF’ workflow rules (signature) table. Therefore, we need to write code to update the flag during the modification process. After writing the code, the ‘Signed’ and ‘Reason’ flags are updated successfully. Refer to below Figure 6.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

     Fig 5. Table dictionary <\/strong><\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

   Fig 6. Signature History <\/strong><\/p>\n\n\n\n

This blog helps us to know about the use By implementing multiple signatures in workflows on different objects, Sage X3 enables you to create sophisticated approval processes that align with your organization’s specific requirements. This promotes better control, compliance, and efficiency in handling critical business operations an how to update the signature history table flags for the custom workflow .<\/p>\n\n\n\n

About Us<\/strong><\/p>\n\n\n\n

Greytrix<\/a> \u2013 a globally recognized Premier Sage Gold Development Partner is a one-stop solution provider for Sage ERP and Sage CRM needs. Being recognized and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development and implementation expertise.<\/p>\n\n\n\n

Greytrix<\/a>\u00a0caters to a wide range of Sage X3 (Sage Enterprise Management) offerings \u2013 a Sage Business Cloud Solution. Our\u00a0unique GUMU™ integrations include\u00a0Sage X3 for Sage CRM,\u00a0Salesforce.com,\u00a0and\u00a0Magento eCommerce\u00a0along with Implementation and Technical Support worldwide for\u00a0Sage X3\u00a0(Sage Enterprise Management). Currently, we are\u00a0Sage X3 Implementation Partner\u00a0in East Africa, Middles East, Australia, and Asia.\u00a0We also offer best-in-class\u00a0Sage X3 customization and development services,\u00a0integrated applications such as\u00a0POS\u00a0|\u00a0WMS\u00a0|\u00a0Payment Gateway\u00a0|\u00a0Shipping System\u00a0|\u00a0Business Intelligence\u00a0|\u00a0eCommerce,\u00a0and have developed add-ons such as\u00a0Catch \u2013 Weight\u00a0<\/a>\u00a0and\u00a0Letter of Credit<\/a>\u00a0for Sage X3 to Sage business partners, end users and Sage PSG worldwide.<\/p>\n\n\n\n

Greytrix is a recognized Sage Rockstar ISV Partner<\/a> for GUMU™ Sage X3 \u2013 Sage CRM integration also listed on Sage Marketplace<\/a>; GUMU™ integration for Sage X3 \u2013 Salesforce is a 5-star app listed on Salesforce AppExchange<\/a>.<\/p>\n\n\n\n

For more information on Sage X3 Integration and Services, please contact us at x3@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

In Sage X3, workflows are used to automate and streamline business processes by defining a sequence of tasks that need to be performed in a specific order. These tasks can involve approvals, reviews, or other actions necessary for the completion of a business process. Workflows in Sage X3 help organizations enforce consistency, reduce manual intervention,\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,5,3162,6,13,7,8,3642,9,10,11],"tags":[4058,1865,2871,4059,3831,2432,4060],"class_list":["post-28639","post","type-post","status-publish","format-standard","hentry","category-configuration","category-features","category-greytrix","category-installation","category-integration","category-miscellaneous-tables","category-sage-erp-x3","category-sage-x3","category-sage-x3-consulting","category-standard","category-tips","tag-assignment-rule","tag-sage-x3-erp","tag-sage-x3-functional-blogs","tag-signature-history","tag-signatures","tag-workflow","tag-x3-workflow"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28639","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=28639"}],"version-history":[{"count":7,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28639\/revisions"}],"predecessor-version":[{"id":29329,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28639\/revisions\/29329"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=28639"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=28639"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=28639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}