As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Hi, I am new to Webfocus. I am developing a maintain application with UPDATE,DELETE and ADD functionality. I want to enable the user to be able to retrieve and display the edited/deleted record. Is there any feature available in maintain that helps us doing the same. It would be very helpful if anyone can provide the pseudocode as well.
Thanks in AdvanceThis message has been edited. Last edited by: <Kathryn Henning>,
8.06 Windows
Posts: 19 | Location: India | Registered: April 24, 2014
I presume you mean during a Maintain session. This would be standard stack manipulation as discussed in the basic Maintain Training course. Please ensure that you undertake this course before developing an application in Maintain.
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007
the user to be able to retrieve and display the edited/deleted record
Thanks for the response. Not really the maintain session. I am able to do that. I need to store both the new record and the edited record in the DB. Something like what the trigger does in SQL. For example there is a row with values : 1,abc,234 The user edits that to: 1, xyz,234 So I would like to see both rows 1, xyz,234 and 1,abc,234 on the form as well as a seperate entry in the DB table.
8.06 Windows
Posts: 19 | Location: India | Registered: April 24, 2014
Maintain does not keep previous versions of the data in the database, unless you tell it to do so. Would you want to keep that last change to the record or all of the changes to the record? If you want to keep all the changes you can set up a CHANGE_DATE field and only INCLUDE records instead of updating. This will keep every iteration of the data.
If you only want to save the last change, you can create a LASTCHANGED field in the data and replace the data in that field every time you do an update on the form.
Those are pretty much your options.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
We never delete anything from a user entry system, too often the user will either make a mistake or try and manipulate the data and then lie about when they made the change. You need an audit trail to deal effectively with those situations.
We use a Data_Entry_Date, Current_Record_Version_Ind and Delete_Flag.
Every entry is inserted with a datetime stamp. If any records exist in the database (for the chosen key) the Current_Record_Version_Ind is set to 0 for those, and the new incoming record is set to 1. If they want to delete the record the Delete_Flag is set to 1 but the data remains in the table.
The data is then only made available through two views, one which is the entire history and one which is the current view and only contains records where Delete_Flag = 0 and Current_Record_Version_Ind = 1.
It works well for us.
WF 7.6.11 Output: HTML, PDF, Excel
Posts: 123 | Location: UK | Registered: October 09, 2003
Tewy is correct in this being the approach to take. Maintain does not contain any features to automate this, but there is no reason that triggers could not be created on the table to achieve this type of transaction. These are outside the control of Maintain and can generally be set on the update, insert and delete actions to create the same scenario.
This can also be done easily in Maintain with include/update stacks and commit/rollback. Done once it becomes second nature to achieve.
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007