Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
a_f:a:view [2022/09/01 01:23] – ↷ Page moved from a_f:3100_actions:view to a_f:a:view administratora_f:a:view [2023/05/09 02:04] (current) – sean
Line 1: Line 1:
-{{tag>Actions Action_List UI Forms}}+{{tag>Index Action Action_List UI Form}}
 ====== VIEW ====== ====== VIEW ======
  
-This action is very similar to the EDIT action. The difference is that the process in which the action has been called does not wait for the user to change the values of the object and continues execution immediately after displaying the form. Also the VIEW action allows viewing the specific presentation of the business object. +This action is very similar to the ''[[a_f:a:edit|EDIT]]'' action. The difference is that the process in which the action has been called does not wait for the user to change the values of the object and continues execution immediately after displaying the form. Also the ''VIEW'' action allows viewing the specific presentation of the business object. 
  
 ===== Syntax ====== ===== Syntax ======
Line 11: Line 11:
  
 ===== Example =====  ===== Example ===== 
-<code aim> VIEW Account</code>+<code aim>VIEW Account </code>
  
 Id() or StringLiteral optionally indicate presentation or form of the business object to be viewed, for example  Id() or StringLiteral optionally indicate presentation or form of the business object to be viewed, for example 
  
-<code aim> VIEW Account USING 'Some fancy presentation'</code>+<code aim>VIEW Account USING 'Some fancy presentation' </code>
  
 where "Some fancy presentation" is the name of the presentation that must be configured with the Account object. where "Some fancy presentation" is the name of the presentation that must be configured with the Account object.
  
 <callout type="primary" icon="true" title="note"> It is possible to optionally indicate the name of the specific section of the business object that will be displayed first, for example: <callout type="primary" icon="true" title="note"> It is possible to optionally indicate the name of the specific section of the business object that will be displayed first, for example:
-<code aim> VIEW Account USING 'Form for administrators' FORM_SECTION 'Personal details'</code></callout>+<code aim>VIEW Account USING 'Form for administrators' FORM_SECTION 'Personal details' </code></callout>
  
 <callout type="primary" icon="true" title="note"> If ''NOEDIT'' keyword is specified at the end of the action the form viewed will have all its input controls disabled, so that the user cannot change any of the values.</callout> <callout type="primary" icon="true" title="note"> If ''NOEDIT'' keyword is specified at the end of the action the form viewed will have all its input controls disabled, so that the user cannot change any of the values.</callout>
  
  • Last modified: 2022/09/13 18:11