OrderHistory Table and Update Tracking

Discussions related to installation and setup of SoftPro products.
Post Reply
ljenkins
Posts: 4
Joined: Tue May 16, 2023 11:37 am

OrderHistory Table and Update Tracking

Post by ljenkins »

The SelectDB.pf.OrderHistory.Description table.field only has information when Requirements and Exceptions are deleted from a Commitment. The Description has only '<Version \>' in it when a Requirement or an Exception is added or updated.

Is it possible to update a setting in SoftPro so that the OrderHistory table shows when a Requirement or an Exception is added or updated?

Is there another way to know when a Requirement or Exception is added or updated other than the OrderHistory table?

Thanks!
ljenkins
Posts: 4
Joined: Tue May 16, 2023 11:37 am

Re: OrderHistory Table and Update Tracking

Post by ljenkins »

If it helps, we are using Version 4.3.60210.119 of SoftPro Select. If you need more table information to answer my question, please let me know.

Thanks!
ljenkins
Posts: 4
Joined: Tue May 16, 2023 11:37 am

Re: OrderHistory Table and Update Tracking

Post by ljenkins »

Here is a screenshot of the Commitment - Schedules B1, B2 screen in SPS. The Requirements and Exceptions we are interested in tracking are on this screen. When a Requirement or an Exception is deleted and the Order saved, the Order History popup window provides information on it. See screenshots for examples.
Attachments
L30 Requirement Deleted.jpg
L30 Requirement Deleted.jpg (72.49 KiB) Viewed 3580 times
Commitment Schedules B1 and B2.jpg
Commitment Schedules B1 and B2.jpg (146.66 KiB) Viewed 3580 times
BobRichards
Posts: 1376
Joined: Wed Jan 15, 2014 3:50 pm
Location: Raleigh, NC
Contact:

Re: OrderHistory Table and Update Tracking

Post by BobRichards »

Sadly there is no easy way to detect changes to these items. The best bet is to create a server package that can detect changes to this area. You have two options:
  • IOrderStore.OrderSaved - You are passed both the saved order and the version immediately before. You can compare any order properties of interest to look for additions/changes/deletions.
  • IOrderStore.OrderSaving - The same as the OrderSaved event but you also have the ability to set a flag and provide a reason to the user if your logic decides the order should not be saved because it breaks some business logic requirement.
Bob Richards, Senior Software Developer, SoftPro
ljenkins
Posts: 4
Joined: Tue May 16, 2023 11:37 am

Re: OrderHistory Table and Update Tracking

Post by ljenkins »

Thank you, Bob!

Much appreciated,
Louise
Post Reply