New Feature – Add an expiration date to your RPA (Restricted Product Authorization)
It is part of Allegion’s continuous effort to look for ways to leverage digital applications to reduce the time to order our products. . We are improving this process for ordering restricted key systems by adding ability to use authorizations more than one time.
Previously, each authorization was a one-time-use only requiring every order for restricted product to be accompanied by a new authorization from the end user. Now, there will be the ability to select various time periods that an authorization can be used. The intent for this change is to allow customers to define their authorization needs to fit their desired level of key control. If an expiration date is not set, all authorizations will default to a one-time-use unless the user selects “Set expiration date” and selects the desired date.
Simply select the new option and add a date when the RPA will expire. There is not an option to “never expire” but the date can be set as far as 50 or 100 years. Don’t worry; if you change your mind, the expiration can be updated by any owner on the account.(Click for example)
To continue using the RPA’s the way they have always worked, keep the One time use option selected and it will only be valid on one order.
On the authorizations tab, RPA’s with an expiration will have an option to expand to see all associated orders. Only an owner can make edits. The expiration date can be modified but the type cannot be changed to one time use. On the other hand, a one time use can be updated to add in an expiration if so desired. (Click for example)
Tip – if there is an old RPA that should not be used, change the type and put it an expiration date.
Comments
0 comments
Please sign in to leave a comment.