13.07.2015 Views

TIBCO MDM Customization Guide - TIBCO Product Documentation

TIBCO MDM Customization Guide - TIBCO Product Documentation

TIBCO MDM Customization Guide - TIBCO Product Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Customizing Record Security| 91Customizing Record SecurityConfiguring Value Based Security for Record ListYou can secure the record list screens (output of repository browse, subsets, andso on.) based on the value of attributes in the records itself. This security appliesto the list of records displayed in the relationship section of the View/Modifyrecord.With this customization, it is possible to completely hide a record from a userusing “hide_record” access, or restrict a user’s edit access to a record by using“view_record”. You need to enhance the repository validation rulebase to do so.Refer to the <strong>TIBCO</strong> Collaboration Information Manager Rulebase <strong>Guide</strong> for moreinformation.Restrictions on Record Access ConditionsFor performance reasons, the of rules containing record level accessactions are converted to SQL in some cases. Therefore, only functions that can betranslated into SQL can be used. These include: and, or, not, eq, neq, lt, leq, gt,geq, defined, undefined.Conditions containing expressions other than those listed above, will fail. Refer tothe <strong>TIBCO</strong> Collaboration Information Manager Rulebase <strong>Guide</strong> for more information.Managing RelationshipsRelationships are used to refer to other record data items. For example, you canspecify that a can, say a can of soda, is contained by a case, and that cases arecontained in a pallet. Relationships can also be used to define record substitutes.<strong>TIBCO</strong> <strong>MDM</strong> allows you to name these relationships, and determine whetherthey are unidirectional or bidirectional. Bidirectional relationships are visiblefrom both the parent and child record. Unidirectional relationships are valid onlyfrom parent to child and not vice-versa, for example, cross-sale.Controlling the Relationships Shown for an Item: ProcedureWhile creating a record and associating it with other records, you can controlwhich relationships apply at a specific step or level. For example, for the mainrecord, all relationships may be valid but for the associated child record, onlysome of the relationships may apply.You can also control the order in which relationships are listed.<strong>TIBCO</strong> <strong>MDM</strong> <strong>Customization</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!