Action Services (client/server)

Action services is a container for custom logic. You could think of action services and its items as class and its methods.

Action services items has built in security support (security logic that could be configured) and used in Screen actions.

Variable initialization logic should be implemented manually via Custom Code.

Each context could contain any quantity of variables of different types.

Server Action Service properties

Section	Name	Description
Basic	Name	Base type of enumerator. All item values should be this type.
Basic	Description	Useful to make notes about purpose of this enumerator.
Security	Anonymous	If checked all action service items could be accessed by anonymous users.

Client Action Service properties

Section	Name	Description
Basic	Name	Base type of enumerator. All item values should be this type.
Basic	Description	Useful to make notes about purpose of this enumerator.

Action Service Item properties

Section	Name	Description
Basic	Name	Base type of enumerator. All item values should be this type.
Basic	Execute Clause	Logical clause that determines if this action is allowed to execute. Notice that this clause is checked on client side (not server). See CanExecute method on server side for server validation.
Basic	Result	Type could be a base type (string, int, etc.), Entity or Enumerator. Type could be single value or an array. Also there is special built in type for service items - Report. Use this result type to automatically open report on client application.
User Interface	Display Name	Name for user interface.
User Interface	Image	Icon for action. Used in windows client. For web client use custom css code.
User Interface	Message	Message to show while long process is running.
User Interface	Confirmation	If set confirmation box is appeared before action execution.
User Interface	Description	Hint message for client button.
Security	Anonymous	If checked all action service items could be accessed by anonymous users.
Security	Execute	Select a permission or built in option for security logic. Built in options: <private> means that this option available only on server side (no controller methods or permission would be created). <auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter.

Created with the Personal Edition of HelpNDoc: Easily create CHM Help documents