$FlsAcc - Revision history

JAL: typos

2015-06-08T15:07:05Z

typos

← Older revision		Revision as of 15:07, 8 June 2015
Line 1:		Line 1:
	<p>		<p>
	The <var>$FlsAcc</var> function, combined with the $<var>$FlsChk</var> function, allows a SOUL request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using variables and values in computation#Resolution of field types and levels\|Resolution of field types and levels]]). </p>		The <var>$FlsAcc</var> function, combined with the <var>[[$FlsChk]]</var> function, allows a SOUL request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using variables and values in computation#Resolution of field types and levels\|Resolution of field types and levels]]). </p>
	<p>		<p>
	$<var>$FlsAcc</var> can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: </p>		<var>$FlsAcc</var> can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 43:		Line 43:

	<li><var class="term">name</var> is optional; use it to control the file or group context of the function. The format for this argument is:		<li><var class="term">name</var> is optional; use it to control the file or group context of the function. The format for this argument is:
	<p class="syntax">[[FILE \| [PERM \| TEMP] GROUP] <span class="term">name</span> [AT <span class="term">location</span>]		<p class="syntax">[[FILE \| [PERM \| TEMP] GROUP] <span class="term">name</span> [AT <span class="term">location</span>] \| $CURFILE \| $UPDATE]
	\| $CURFILE \| $UPDATE]
	</p>		</p>
	<p>If access for the current file of a FOR loop is desired, $Curfile can be used as the second argument. $Update can be used to indicate the name of the update file in the current group. $Curfile and $Update are described in detail in [[Files, groups, and reference context#$Curfile and $Update functions\|$Curfile and $Update functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, <var>$FlsAcc</var> returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. </p>		<p>If access for the current file of a FOR loop is desired, <var>$Curfile</var> can be used as the second argument. <var>$Update</var> can be used to indicate the name of the update file in the current group. <var>$Curfile</var> and <var>$Update</var> are described in detail in [[Files, groups, and reference context#$Curfile and $Update functions\|$Curfile and $Update functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, <var>$FlsAcc</var> returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. </p>
	</li>		</li>
	</ul>		</ul>

	[[Category:SOUL $functions]]		[[Category:SOUL $functions]]

JAL: link repair

2015-05-13T22:23:00Z

link repair

← Older revision		Revision as of 22:23, 13 May 2015
Line 1:		Line 1:
	<p>The $~~FLSACC~~ function, combined with the $~~FLSCHK~~ function, allows a ~~User Language~~ request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using variables and values in computation#Resolution of field types and levels\|Resolution of field types and levels]]"). </p>		<p>
	<p>$~~FLSACC~~ can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: </p>		The <var>$FlsAcc</var> function, combined with the $<var>$FlsChk</var> function, allows a SOUL request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using variables and values in computation#Resolution of field types and levels\|Resolution of field types and levels]]). </p>
			<p>
			$<var>$FlsAcc</var> can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 10:		Line 12:
	<td>SELECT access rights</td>		<td>SELECT access rights</td>
	</tr>		</tr>

	<tr>		<tr>
	<td> R</td>		<td> R</td>
	<td>READ access rights</td>		<td>READ access rights</td>
	</tr>		</tr>

	<tr>		<tr>
	<td> U</td>		<td> U</td>
	<td>UPDATE access rights</td>		<td>UPDATE access rights</td>
	</tr>		</tr>

	<tr>		<tr>
	<td> A</td>		<td> A</td>
Line 23:		Line 28:
	</tr>		</tr>
	</table>		</table>
	~~<b>~~Syntax~~</b>~~
	<p>The format of the $~~FLSACC~~ function is:</p>		==Syntax==
	<p class="~~code~~">$~~FLSACC~~ (fieldname <~~var~~>[</~~var~~>,name<~~var~~>])</~~var~~>		<p>
			The format of the <var>$FlsAcc</var> function is:</p>
			<p class="syntax">$Flsacc (<span class="term">fieldname</span> <span class="squareb">[</span>,<span class="term">name</span><span class="squareb">]</span>)
	</p>		</p>
	<p>~~where~~:</p>		<p>
			Where:</p>

	<ul>		<ul>
	<li>fieldname is a character string that is interpreted as the name of the field whose access is being checked. ~~</li>~~		<li><var class="term">fieldname</var> is a character string that is interpreted as the name of the field whose access is being checked.
	<p>If this argument is omitted or null, every field in the file or group specified in the name argument is checked. In this case, the output string returned by $~~FLSACC~~ contains an access indication (S, R, U, A) only if that level of access applies to every field in the file or group. This use of $~~FLSACC~~ is costly system overhead because all field descriptions must be examined.</p>		<p>If this argument is omitted or null, every field in the file or group specified in the name argument is checked. In this case, the output string returned by <var>$FlsAcc</var> contains an access indication (S, R, U, A) only if that level of access applies to every field in the file or group. This use of <var>$FlsAcc</var> is costly system overhead because all field descriptions must be examined.</p>
	</li>		</li>

	<li>name is optional; use it to control the file or group context of the function. The format for this argument is:~~</li>~~		<li><var class="term">name</var> is optional; use it to control the file or group context of the function. The format for this argument is:
	<p class="~~code~~">[[FILE \| [PERM \| TEMP] GROUP] name [AT location]		<p class="syntax">[[FILE \| [PERM \| TEMP] GROUP] <span class="term">name</span> [AT <span class="term">location</span>]

	\| $CURFILE \| $UPDATE]		\| $CURFILE \| $UPDATE]
	</p>		</p>
	<p>If access for the current file of a FOR loop is desired, $~~CURFILE~~ can be used as the second argument. $~~UPDATE~~ can be used to indicate the name of the update file in the current group. $~~CURFILE~~ and $~~UPDATE~~ are described in detail in [[Files, groups, and reference context#$~~CURFILE~~ and $~~UPDATE~~ functions\|$~~CURFILE~~ and $~~UPDATE~~ functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, $~~FLSACC~~ returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. </p>		<p>If access for the current file of a FOR loop is desired, $Curfile can be used as the second argument. $Update can be used to indicate the name of the update file in the current group. $Curfile and $Update are described in detail in [[Files, groups, and reference context#$Curfile and $Update functions\|$Curfile and $Update functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, <var>$FlsAcc</var> returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. </p>
	</li>		</li>
	</ul>		</ul>

	[[Category:SOUL $functions]]		[[Category:SOUL $functions]]

Mlarocca: Mlarocca moved page $FLSACC to $FlsAcc: Lower case change

2014-07-21T17:46:14Z

Mlarocca moved page $FLSACC to $FlsAcc: Lower case change

← Older revision	Revision as of 17:46, 21 July 2014
(No difference)

JAL at 20:38, 2 January 2014

2014-01-02T20:38:42Z

← Older revision		Revision as of 20:38, 2 January 2014
Line 28:		Line 28:
	</p>		</p>
	<p>where:</p>		<p>where:</p>

	<ul>		<ul>
	<li>fieldname is a character string that is interpreted as the name of the field whose access is being checked. </li>		<li>fieldname is a character string that is interpreted as the name of the field whose access is being checked. </li>
	<p>If this argument is omitted or null, every field in the file or group specified in the name argument is checked. In this case, the output string returned by $FLSACC contains an access indication (S, R, U, A) only if that level of access applies to every field in the file or group. This use of $FLSACC is costly system overhead because all field descriptions must be examined.</p>		<p>If this argument is omitted or null, every field in the file or group specified in the name argument is checked. In this case, the output string returned by $FLSACC contains an access indication (S, R, U, A) only if that level of access applies to every field in the file or group. This use of $FLSACC is costly system overhead because all field descriptions must be examined.</p>
	</li>		</li>

	<li>name is optional; use it to control the file or group context of the function. The format for this argument is:</li>		<li>name is optional; use it to control the file or group context of the function. The format for this argument is:</li>
	<p class="code">[[FILE \| [PERM \| TEMP] GROUP] name [AT location]		<p class="code">[[FILE \| [PERM \| TEMP] GROUP] name [AT location]
Line 37:		Line 39:
	\| $CURFILE \| $UPDATE]		\| $CURFILE \| $UPDATE]
	</p>		</p>
	<p>If access for the current file of a FOR loop is desired, $CURFILE can be used as the second argument. $UPDATE can be used to indicate the name of the update file in the current group. $CURFILE and $UPDATE are described in detail in [[Files, ~~Groups~~, and ~~Reference Context~~#$CURFILE and $UPDATE functions\|$CURFILE and $UPDATE functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, $FLSACC returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. </p>		<p>If access for the current file of a FOR loop is desired, $CURFILE can be used as the second argument. $UPDATE can be used to indicate the name of the update file in the current group. $CURFILE and $UPDATE are described in detail in [[Files, groups, and reference context#$CURFILE and $UPDATE functions\|$CURFILE and $UPDATE functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, $FLSACC returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. </p>
	</li>		</li>
	</ul>		</ul>

	[[Category:SOUL $functions]]		[[Category:SOUL $functions]]

JAL at 23:58, 1 January 2014

2014-01-01T23:58:49Z

← Older revision		Revision as of 23:58, 1 January 2014
Line 1:		Line 1:
	<p>The $FLSACC function, combined with the $FLSCHK function, allows a User Language request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using ~~Variables~~ and ~~Values~~ in ~~Computation~~#Resolution of field types and levels\|Resolution of field types and levels]]"). </p>		<p>The $FLSACC function, combined with the $FLSCHK function, allows a User Language request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using variables and values in computation#Resolution of field types and levels\|Resolution of field types and levels]]"). </p>
	<p>$FLSACC can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: </p>		<p>$FLSACC can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: </p>
	<table>		<table>

Alex: Automatically generated page update

2013-04-20T13:19:03Z

Automatically generated page update

New page

The $FLSACC function, combined with the $FLSCHK function, allows a User Language request to check for field-level security access violations before they occur. This reduces evaluation-time errors and request cancellations, and it helps to ensure that the files being updated are not left in a logically inconsistent state ([[Using Variables and Values in Computation#Resolution of field types and levels|Resolution of field types and levels]]"). 
$FLSACC can determine a user's access rights to a particular field or to all fields in a file or group. The function returns a character string representing the user's access rights to the specified field(s). If the field is not defined in the file or group, a null string is returned. The string normally contains a combination of the characters listed in this table: 
<table>
<tr class="head">
<th>Character</th>
<th>Meaning</th>
</tr>
<tr>
<td> S</td>
<td>SELECT access rights</td>
</tr>
<tr>
<td> R</td>
<td>READ access rights</td>
</tr>
<tr>
<td> U</td>
<td>UPDATE access rights</td>
</tr>
<tr>
<td> A</td>
<td>ADD access rights</td>
</tr>
</table>
Syntax
The format of the $FLSACC function is:
$FLSACC (fieldname <var>[</var>,name<var>])</var>

where:
<ul>
<li>fieldname is a character string that is interpreted as the name of the field whose access is being checked. </li>
If this argument is omitted or null, every field in the file or group specified in the name argument is checked. In this case, the output string returned by $FLSACC contains an access indication (S, R, U, A) only if that level of access applies to every field in the file or group. This use of $FLSACC is costly system overhead because all field descriptions must be examined.
</li>
<li>name is optional; use it to control the file or group context of the function. The format for this argument is:</li>
[[FILE | [PERM | TEMP] GROUP] name [AT location]

| $CURFILE | $UPDATE]

If access for the current file of a FOR loop is desired, $CURFILE can be used as the second argument. $UPDATE can be used to indicate the name of the update file in the current group. $CURFILE and $UPDATE are described in detail in [[Files, Groups, and Reference Context#$CURFILE and $UPDATE functions|$CURFILE and $UPDATE functions]]. For single file context, the field level security access rights are well defined. If a field name is specified in group context, $FLSACC returns the maximum access rights for the group. If the name argument is omitted or null, the context used for the check is the context of the statement that contains the function. 
</li>
</ul>
[[Category:SOUL $functions]]