{"id":24755,"date":"2022-02-28T09:40:30","date_gmt":"2022-02-28T09:40:30","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=24755"},"modified":"2022-02-28T09:40:34","modified_gmt":"2022-02-28T09:40:34","slug":"how-to-set-dynamic-status-field-on-screen-based-on-date-range","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2022\/02\/28\/how-to-set-dynamic-status-field-on-screen-based-on-date-range\/","title":{"rendered":"How to set dynamic Status field on screen based on date range"},"content":{"rendered":"\n

In Sage X3<\/a>, one of the client\u2019s requirement was to have a dynamic \u201cPolicy Status\u201d field which will reflect the current status where the policy is Active or De-active for the selected module. Here another condition was that at a given time span only one policy per module can be kept Active, rest will stay deactivated and will get activated automatically once the date condition is satisfied.<\/p>\n\n\n\n

First to navigate to the screens that\u2019ll be used for the below steps:<\/p>\n\n\n\n

Window management: All -> Development -> Script dictionary -> Window management
Script editor: All -> Development -> Script dictionary -> Scripts -> Script editor
Tables: All -> Development -> Data and parameters -> Tables<\/p>\n\n\n\n

To fulfill the above mentioned requirement we need to follow the below steps:<\/p>\n\n\n\n

Step 1: Below are the locations showing the \u201cStatus and Applicable module\u201d fields on screen, on window management and on the linked table of the screen. Refer the screenshots for reference:<\/p>\n\n\n\n

New Stuff:<\/strong> Validation on the Sales order screen if credit limit exceeds<\/a><\/p>\n\n\n\n

\"Module<\/a><\/center>\n
Module and Status fields on screen<\/center><\/font>\n\n\n\n
\"Status<\/a><\/center>\n
Status field under Header tab in Window management<\/center><\/font>\n\n\n\n
\"Status<\/a><\/center>\n
Status field in linked table of Header screen<\/center><\/font>\n\n\n\n

Step 2: For this customization we need to add some action events. The script code for the screen can be identified from Window management > Header screen > Specific script.<\/p>\n\n\n\n

The logic for them will be as follows:
Once the user clicks the \u201cNew\u201d button on screen to create a new policy and selects the Applicable Module our logic part will trigger that will check whether there is any existing Policy already for the given Module and if it does then whether it\u2019s currently Active or Inactive.
In case the Policy exists and is Active, the Status field is made non-editable using the DISZO command followed by AFFZO command and set to DEACTIVE. Whereas if the Policy exists but is in Inactive status, then it\u2019ll allow the user to select the status as per choice.<\/p>\n\n\n\n

\"Case<\/a><\/center>\n
Case of Active existing Policy on module<\/center><\/font>\n\n\n\n

Step 3: Now when a new policy is created for a given date range, then another logic is added on the LIENS action event in script which gets triggered whenever the Entry no. is browsed from left list selection or opening the screen.<\/p>\n\n\n\n

This logic checks if the current date is within the Policy date range first and then:
If the current date is within the date range then it\u2019ll check if the status is Active or De-active.
For the Active case the logic will return from the event without any change.
For the De-active case the logic will check if there is any existing Active policy for the module, if not then it\u2019ll change the status to ACTIVE on the screen and trigger an Update instruction on the table.<\/p>\n\n\n\n

If the current date exceeds the To date of Policy:
For the Active case the logic will change the status to DEACTIVE and make the field non-editable using the DISZO command followed by AFFZO command, and update the table using the Update instruction.
For the De-active case logic will return from the event without any change.<\/p>\n\n\n\n

This way we can dynamically set the status field on screen based on the policy date range.<\/p>\n\n\n\n

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

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

Greytrix has some unique integration solutions developed for Sage CRM<\/a> with Sage ERPs namely Sage X3<\/a>, Sage Intacct<\/a>, Sage 100<\/a>, Sage 500<\/a>, and Sage 300<\/a>. We also offer best-in-class Sage ERP and Sage CRM customization and development services to Business Partners, End Users, and Sage PSG worldwide. Greytrix helps in the migration of Sage CRM from Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes addons like  Greytrix Business Manager, Sage CRM Project Manager, Sage CRM Resource Planner, Sage CRM Contract Manager, Sage CRM Event Manager, Sage CRM Budget Planner, Gmail Integration, Sage CRM Mobile Service Signature, Sage CRM CTI Framework.<\/p>\n\n\n\n

Greytrix is a recognized Sage Champion Partner for GUMU™ Sage X3 \u2013 Sage CRM integration listed on Sage Marketplace<\/a> and Sage CRM \u2013 Sage Intacct integration listed on Sage Intacct Marketplace<\/a>. The GUMU™ Cloud framework<\/a> by Greytrix forms the backbone of cloud integrations that are managed in real-time for the processing and execution of application programs at the click of a button.<\/p>\n\n\n\n

For more information on our integration solutions, please contact us at sage@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

In Sage X3, one of the client\u2019s requirement was to have a dynamic \u201cPolicy Status\u201d field which will reflect the current status where the policy is Active or De-active for the selected module. Here another condition was that at a given time span only one policy per module can be kept Active, rest will stay\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":[8,13],"tags":[504,3578,3573,1098,3579,1977],"class_list":["post-24755","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-date","tag-dynamic-change","tag-insurance","tag-inventory","tag-policy","tag-sales"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/24755","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=24755"}],"version-history":[{"count":11,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/24755\/revisions"}],"predecessor-version":[{"id":24771,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/24755\/revisions\/24771"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=24755"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=24755"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=24755"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}