Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This function will define one EDMprotectedData item in an EDMdataModel. An EDMprotectedData item can be one entityInstance, one instance type (one entity) or one instance type and all its sybtypes. The EDMprotectedData description is stored as "meta-data" in the actual model. This meta-data is implemented using USER_DEFINED_ENTITY. 

Info

...

Be aware of the options EXCLUDE_USER_DEFINED_ENTITIES and  ONLY_USER_DEFINED_ENTITIES in the EDMwriteStepFile operations

...

 

The xpxDefineProtectedData() operation can only be successfully performed for callers that have ADMINISTRATOR rights to the actual model. The xpxDefineProtectedData() must be performed in an open EDMwriteTransaction.  Any "condition" argument in the following functions are any legal EDMexpressX logical functions. Such expressions may contain invocations of any functions in the actual EDMmethodSchema (EDMquerySchema, EDMruleSchema, EDMmapSchema), in the actual underlying Express schema, any EDMsystemQuery, any built-in EDMexpressX functions, any Express built-in schema.  The following constants are implemented for being used in such "conditions":

 

...

xpxCREATE

...

_ACCESS

...

XPXSUPERUSERID

...

...

XPXCURRENTAGGRINDEX

     XPXCURRENTAGGRID, XPXNEWAGGRELEMENTVALUE

 

...

XPXAPPEND_AGGR

...

_ELEMENTXPXDELETE_AGGR_ELEMENT_BY_INDEX

...

xpxWRITE_ACCESSXPXCURRENTGROUPIDXPXCURRENTAGGRIDXPXADD_AGGR_ELEMENT

...

XPX_INSERT_AGGR_ELEMENT

...

_BEFORE_INDEX
xpxREAD_ACCESSXPXCURRENTATTRIBUTEVALUEXPXNEWAGGRELEMENTVALUEXPXGET_AGGR_ELEMENT_BY_INDEX

...

 
xpxDELETE_ACCESSXPXNEWATTRIBUTEVALUEXPXCREATE_AGGRXPXGET_AGGR_ELEMENTS

...

 
xpxSELECT_ACCESSXPXCURRENTATTRIBUTEIDXPXGET_AGGR_

...

MEMBER_COUNTXPXPUT_AGGR_ELEMENTS

...

 

...

XPXCURRENTUSERIDXPXCURRENTOPERATIONXPXPUT_AGGR_ELEMENT_BY_INDEX

...

XPXDELETE_

...

AGGR_

...

ELEMENTS_

...

BY_

...

VALUE 

 

Arguments

...

1TypeNameComment
2GENERICmodelIdThe EDMdataModel to define the actual ProtectedData for Only ADMINISTRATOR's of the model are permitted to perform this operation successfully The actual EDMdataModel must be in an open EDMwriteTransaction
3GENERICinstanceTypeNameOrInstanceTypeIdOrInstanceIdAn EntityInstanceId, an InstanceTypeId (entityId) or an InstanceTypeName (EntityName) that defines the EDMprotectedData item.
4INTEGERpermittetOperations

Any combinations of     xpxCREATE_ACCESS, xpxWRITE_ACCESS, xpxREAD_ACCESS, xpxDELETE_ACCESS, xpxSELECT_ACCESS .The default value is all set, i.e., all operations are legal

5STRINGcreateCondition

Any legal textual logical EDMexpressX expression that be evaluated before an xpxCREATE_ACCESS operation. This operation must be evaluated to TRUE before the actual operation can be performed. The default value is NULL = no condition = TRUE

6STRINGdeleteConditionSame as "createCondition" but for xpxDELETE_ACCESS operations
7STRINGwriteConditionSame as "createCondition" but for xpxWRITE_ACCESS operations
8STRINGreadConditionSame as "createCondition" but for xpxREAD_ACCESS operations
9STRINGaggrOperationsConditionSame as "createCondition" but for any operations on aggregates
10STRINGselectConditionSame as "createCondition" but for xpxSELECT_ACCESS operations
11STRINGselectConditionFilterCondition that will be "AND(ed)" to the conditions specified by the caller in an xpxSELECT_ACCESS operation the default value is NULL, i.e., no condition will be "AND(ed)" to the user specified select operation condition.
12INTEGERoptionsDefault value is xpxEXCLUDE_ATTRIBUTES
13GENERICattributeNameOrAttributeIdNAttributeId or attributeName
14INTEGERattributeNOperations

Permitted operation on attribute, i.e., xpxREAD_ACCESS or xpxWRITE_ACCESS. Default is xpxREAD and xpxWRITE

15STRINGattributeNCondition

Condition that will be evaluated before any access to this specified attribute. The default value is NULL = no condition = TRUE

...