This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
-> Reopen framework in workbench again.
-> Check the command is still defined in Command definitions.
-> Check the command reference still exists in the business object.
-> Force a save or make a dummy change and resave to regenerate the VLF-ONE dat file.
Does that make the command missing problem go away?
There is also an option on the new Common Activities tab to add a new command to a business object.
I think its just doing a second save and restart that causes an internal table to get rebuilt.
- Add new command.
- Save and restart.
- Open again.
- Dummy change (eg: version number) or just force a resave.
- Open again and run VLF-ONE app.
Problem should go away.
Okay – this seems to circumvent the problem.
• Add new command definition
• Add the new command's reference to business object(s) + snap in command handler.
• Use save and restart.
• Immediately save and restart again (2nd time) – elect to force a new save to regenerate VLF-ONE DAT file.
• Now execute VLF-ONE application.
Alternatively use the Custom command on the business object’s Common Activities tab – but that will create a command handler stub that you would have to delete.