Step 1: Create an activity to assemble the values Reference the control rule in a flow action, harness, section, or other HTML rule, identifying a property presented to the user in read-write mode (input mode).Include a element with extended attributes as defined below. Create a control rule containing the appropriate JavaScript functions.See Harness and Section forms - Defining a Dynamic Select control for a field. If your application can obtain the needed data using a clipboard page, report definition, or list view rule, it is easier to configure the Dynamic Select controls directly in the harness, section, or flow action form, rather than using an activity. Find or create an activity that creates an XML document containing the list of values to appear at runtime.Although you can complete the steps in any order, this order is recommended: The clipboard property associated with the input field is updated to contain a value determined by the user's selection.Ĭomplete three steps to configure a Dynamic Select control.The user selects an item from the drop-down list.A JavaScript function on the workstation presents the list, without repainting the entire form.The server sends the XML document to a user workstation.After the server receives the message, the server executes an activity to produce an XML document listing both the text values that form the list and a value for each.A JavaScript function executes on the workstation, sending a short HTTP message to the Pega 7 Platform server.The user places focus on an input field on a form that contains the Dynamic Select control. Execution sequenceĪt runtime, a use of a Dynamic Select control has seven steps: Alternatively, select Field Value as the Table Type, and include the values as a set of field value rules. Instead, on the General tab of the Property form, select Local List as the Table Type and provide the values on that tab. Overviewĭon't use the Dynamic Select control to present a static list. That approach is simpler and easier to build and test than the older approach described here. You can configure most Dynamic Select controls in a harness, section, or flow action directly, while completing the Harness, Section, or Flow rule form. You can specify the following sources for the values appearing in the list: In contrast, a Dynamic Select control can present a list that depends on the user's role, the date, the filtered results of a database query, and other factors. The standard HTML element presents a fixed list of choices to a user who is completing a form, for example sizes S, M, L, XL, and XXL. The Dynamic Select control is an HTML element with additional attributes and capabilities. However, users working on purchase orders should not lock out users working on the parent purchase request cases.You are here: User interface > User interface rules > Harness and section forms > Dynamic Select controls - Internal operations and advanced features Dynamic Select controls - Internal operations and advanced features The company has determined that only one user at a time may open and work on a case. Your application contains a top-level case type names Purchase Request and a Purchase Order child case. The client application receives the request The service listener sends the response back to the application that made the requestġ1. The service listener receives the response from the Service APIġ0. The service rule maps the clipboard data to form the response data, using the XML Parser ruleĩ. Control is passed to the service activity, which provides the logic for the serviceĨ. The request is mapped, using the instance of an XML Parser rule, onto the clipboard according to the specifications contained in the service ruleħ. Once authenticated, service processing continues using the authenticated user's access group, not the access group that is contained in the service packageĦ. Pega then establishes the service requestor and optionally performs authentication based on security credentials that are passed in the request. Pega looks up the service package and related service rule, using the access group specified in the service packageĥ. Then, the Service API hands control over to PegaĤ. The service listener receives the request and instantiates the Service API to provide communication with Pega. This functionality is provided by either the Web Server, Application Server, or Pega Listenerģ. The service listener listens for incoming requests. A client application sends a request to your applicationĢ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |