As the development growth of Valence apps grows over time and in a multiple release, multiple instance environment, it can be a challenge, if not impossible, to keep App Master and Group Master identical and in-sync between them all. When trying to use vvSecure_isAuthorized or vvSecure_isMember, having to hard code AppID# and GroupID# can be messy.
Having the ability to be able to retrieve a GroupId# and an AppId# by name would help alleviate hard coding numbers and make transition to new releases easier. More often the group names and app names will be the same but the id number will not.
Being able to use vvUtility_getGroupId() in conjunction with vvSecure_isMember() and vvUtility_getAppId() in conjunction with vvSecure_isAuthorized() is what I had in mind.
Having the ability to be able to retrieve a GroupId# and an AppId# by name would help alleviate hard coding numbers and make transition to new releases easier. More often the group names and app names will be the same but the id number will not.
Being able to use vvUtility_getGroupId() in conjunction with vvSecure_isMember() and vvUtility_getAppId() in conjunction with vvSecure_isAuthorized() is what I had in mind.
Comment