SoftwareShield
System Feature Guide > Authorization
Definitions > Authorization
Definition Composite Payload > Design Time Payloads
Design Time PayloadsThe Authorization Definitions that are contained inside the Design-Time Composite are collectively called a "payload". Individually, each one is called a "leaf" Authorization Definition. You can view the composite as a "tree" with only one level of branches, but an arbitrary number of them. Each branch, points to an individual leaf Authorization Definition. Each leaf Authorization Definition in the payload may also use a parameter value that is stored with it (if required). You must define the entire payload of a Design-Time Composite Authorization Definition at "design-time" (when you are designing your license). There is a minor exception to this rule regarding using parameter values taken from User Defined Fields at run-time, see below. When activated, each of the leaf definitions is immediately and individually activated (in Authorization ID order) using the appropriate parameter value (if any). Parameter values for leaf Authorization Definitions can be numeric type or date type, as required by the individual Authorization Definition type of that leaf. Parameter values for leaf Authorization Definitions can be either defined at design-time as a constant value, or can be taken at run-time, during activation, from the numeric or date value stored in a User Defined Field. However, the decision for the source of the parameter must also be made at design-time. Only one type of Authorization Definition is not an eligible candidate for being used in the payload of a Design-Time Composite Authorization Definition: the Run-Time Composite Authorization Definition. More InformationFor help on actually defining design-time payloads, see Creating Composite Definitions in the SoftwareShield License Manager Reference. For help on setting initial values of the User Defined Fields (numeric and date types), see User Defined Fields Tab in the SoftwareShield License Manager Reference. For help on setting and getting values stored in User Defined Fields at run time, see SetUDDate, GetUDDate, SetUDNumber and GetUDNumber in the SoftwareShield ClientProtector Reference. |