Keep Last Value selected:<\/u><\/em> Will keep the last value entered by the end user selected.<\/p>\nSelect only from list:<\/u><\/em> end user will not be able to enter any data manually and he will just forced to select from the list of values. of course this option will be enabled only of we selected the prompt with list of values option.<\/p>\nOptional prompt:<\/u><\/em> If this option is selected the end use will be able to skip this prompt. the value will be considered only if the end user selected a value for this prompt.<\/p>\nAdvanced Side Notes:<\/strong><\/p>\n\n- Universe Design Tool (UDT) or AKA legacy BO designer will work best with the 5 main parameters.\u00a0 If you do not use these extra parameters in the designer that will parse OK. Infact sometimes it might not recognize all the 8 parameters so it is best to stick to the main 5 at the universe level but it will work fine with all 8 Parameters.<\/li>\n<\/ul>\n
Example @Prompt(\u20181) Enter Country Name\u2019,\u2019A\u2019,\u2019Country Dimension\\Country Name\u2019,multi,free,[Not_Persistent],[<{default_value(s)or leave_blank}>],[User:#]<\/strong>)<\/p>\nPrompt Persistence:<\/strong> <\/span>Default value is \u201cPersistent\u201d; however, the value \u201cNot_Persistent\u201d is needed on the prompt value for any Personally Identifying Information (PII). WebI report writers want to use this syntax but the designer might fault this as a parameter issue in UDT or Designer.\u00a0 Using \u201cNot_Persistent\u201d removes the last prompted value in the report parameter.\u00a0 It force purges the value.\u00a0 This can be very important for security and regulatory reasons.\u00a0 Leaving values especially if it is personal data can open up possible General Data Protection Regulation (GDPR) issues.<\/p>\nDefault Value(s):<\/strong><\/span> If left blank no default value used.\u00a0 If a value or values is desired then the set should be surrounded by { } characters and separated by commas (much like hard-coded LOV values earlier in the @Prompt parameters).\u00a0 This optional parameter can serve as a manual override to the values coming from the database and short list the values to do so row level security or simplification in your Web Intelligence report prompt.\u00a0 Some Report Developers find that using this option with the \u201cNot_Persistent\u201d option provides business value in the workflow of the webi reports.<\/p>\nUser:#:<\/strong> <\/span>This is very useful when you have more than 1 prompt that appears when the refresh is invoked.\u00a0 It allows the business objects universe\u00a0 developer to define the relative order of the prompt.\u00a0 If two prompts have the same \u201cUser:#\u201d value then they are sorted alphabetically.\u00a0 This is typically coded at the report level since the UDT might complain about the prompt values depending on which part of the SQL predicate the prompt parameters is being evaluated.<\/p>\n\n- As of BO v4.1.x usage of LOV parameter ie Parm3 if used in a derived table will not parse.<\/strong> I suspect the SQL regeneration will parse the @Prompt in the FROM clause instead of the WHERE predicate.\u00a0 While it can do so without error if the LOV (parm3) is blank or with static default values, it will fail while trying to parse a valid LOV ‘class\/object’ in the derived table.<\/li>\n<\/ul>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Legacy Business Object v3.x to v6.5 introduced the @prompt variable to parameterize the universe and reports.\u00a0 This design gave rise to reporting flexibility.\u00a0 Many users built very creative reporting solutions with the use of the @Prompt variable across declarative reporting templates.\u00a0 This variable code can look very confusing at first but over time it will […]<\/p>\n","protected":false},"author":2,"featured_media":4330,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30],"tags":[],"class_list":["post-4324","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bi-business-objects"],"jetpack_featured_media_url":"https:\/\/www.designandexecute.com\/designs\/wp-content\/uploads\/2018\/08\/prompt-wizard.jpg","_links":{"self":[{"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/posts\/4324","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/comments?post=4324"}],"version-history":[{"count":6,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/posts\/4324\/revisions"}],"predecessor-version":[{"id":4390,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/posts\/4324\/revisions\/4390"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/media\/4330"}],"wp:attachment":[{"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/media?parent=4324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/categories?post=4324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.designandexecute.com\/designs\/wp-json\/wp\/v2\/tags?post=4324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"business-objects-prompt-example\"](\"http:\/\/www.designandexecute.com\/designs\/wp-content\/uploads\/2018\/08\/business-objects-prompt-example.gif\")
<\/a><\/p>\n