...
targetPage: string. Name of Page to be redirected to. In Groovy logic code, this parameter is sometimes provided as an argument of a method call, instead of providing this parameter directly. The page names are defined as values of constants available in AppPages interface.targetPageAction: string = “RECALCULATE” | “SUBMIT” | “WITHDRAW" | “APPROVE” | “REJECT” | “DUPLICATE”. Action to be triggered on targetPage. For objects of types Q, CT, RBA, CO. Quotes also support “CONVERT_TO_DEAL” | “MARK_AS_LOST”. Custom Forms support “RECALCULATE“ | “SUBMIT“ | “WITHDRAW" | “APPROVE” | “REJECT” (Withdraw, Approve and Reject since version 13.0). Price Lists and Live Price Grids support “RECALCULATE” (since version 13.0).targetPageAddLostReason: boolean. Displays a confirmation dialog with options to set lost reason and lost reason comment for Quote context linking event, when using targetPageAction = 'MARK_AS_LOST' (since version 13.0).targetPageEntityType: string. Unique name of configured CLIC header type (Quote Type, Agreement & Promotion Type, Rebate Agreement Type, Compensation Type). Can be also used for Custom Form Types.targetPageFields: [key:value] Values for out-of-the-box fields of the target page entity.targetPageFilters: Applies a simple or an advanced filter to the target page table. Filtering is supported for the following tables (listings): Quotes, Agreements & Promotions, Price Records, Rebates Agreements, Rebates Records, Compensation Plans, Compensation Records, Price Lists, Live Price Grids, Manual Price Lists, Custom Forms.
If you use the “&" character in a quick filter, you need to encode it manually (%26) (as it is used to separate query string parameters).
Example:?tpFilters=sku%20~%200005(sku contains 0005). For more details, see the ContextLinkingURLParams documentation.targetPageInputs: [key:value] Map with values for the input fields/parameters of the target page entity. The inputs can be of both simple and also complex types like Configurator. For example, in case of Configurator, the “key” represents the name of the Configurator input, and the “value” will be a Map with values of the inputs of the Configurator form.
To set the value of an input nested in a collapsible section, use dot notation.
Example:Code Block language groovy targetPageInputs: [ // Sets the value of the 'stringUserEntry1_collapsible_row1' input within 'row1' in 'collapsibleSectionWithRows' to "Hello". "collapsibleSectionWithRows.row1.stringUserEntry1_collapsible_row1": "Hello" ]
...