A new configuration table /BTI/MDE_C_WRPRI has been added to BDEx to allow for prioritization rules to be set up for Work Requests in terms of their Primary Master Data Object.
This can be useful for some Work Request types, such as BPEM Cases, where the potential Master Data Objects associated with them might vary from time to time or where the expected Primary Master Data Object might be sub-optimal in terms of Customer identification when other alternative object references are available.
In the example below the BPEM Case displayed has been configured with the Installation as a Primary Object, however there is also a Billing Document attached as a secondary reference:
Using the new Work Request Priorities configuration settings an entry can be made to ‘prefer’ the Billing Document details over the Installation details if they are available when launching BDEx. This configuration is found in table /BTI/MDE_C_WRPRI:
With these settings in force BDEx will attempt to infer the Primary Object at runtime using the Billing Document details if it can. In this example below the BDEx has used the Billing Document to determine that the Contract is the correct context to use: