• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

vvUtility_getAppId vvUtility_getGroupId

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • vvUtility_getAppId vvUtility_getGroupId

    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.

  • #2
    This would be ideal. It would also be helpful to have a user defined field(?) (20 chars?) in VVAPPS. This would allow any APP's ID to be accessed via a known key and could be used to softcode application launching, closing, etc. It would also be nice to have a couple user defined field in VVAPPS.

    Comment

    Working...
    X