IMPORTANT: Five nested dialogs are necessary to complete this step. In the second (Edit) dialog, you choose Invoke Function, and in the third (not shown), you choose Remove Manager from the available list of functions. Back in the Edit - Context Entry “removed” dialog, you choose selectedManager and company as input keys in the Edit - Parameter dialogs (also not shown).
In most designs, the table appears in a grid that holds the table along with other related views. We place the table in such a grid to complete the tutorial. Creating a dashboard is not covered in previous tutorials, so all that needs explaining here is the context entry. A structure is needed to hold the list of managers. By creating an instance of a company object in the dashboard, we also create a manager array that is initially null. Nonetheless, we can get a reference to it and create an empty list of managers the first time the Add Manager function is called. After that, manager entries can populate the list.
Note that the storage type for the company object is user, which means each different logon name has a different company object that is kept until the server is restarted. See the Web Component Guide for information about the available storage mechanism choices.
This tutorial introduces the usage of Bean Input components as a way of collecting data. Notice that very few context keys were declared, which makes it a much more efficient mechanism for collecting and storing data, especially when large amounts of data inputs are required.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー