Automated service request and live input validation
Kristoffer_Stormark
Customer IT Monkey ✭
This is for all of you out there playing with automation
How do you handle the following.
Doing automation with fixed values are not a problem, and works well but now we are getting into more advance automation.
and the we wonder what other do about it.
As an example we would like a RO for a Shared Mailbox.
The user have to choose a alias for this mailbox, in there in lay our problem.
Are there any way og validating the availability of any given alias at the time of creation.
Or how do you handle this
Failed the SR if alias already taken
Pause with review activity
or ?
This is not a question about the exchange side this can be for any product where the end user have to choose.
/Kristoffer
How do you handle the following.
Doing automation with fixed values are not a problem, and works well but now we are getting into more advance automation.
and the we wonder what other do about it.
As an example we would like a RO for a Shared Mailbox.
The user have to choose a alias for this mailbox, in there in lay our problem.
Are there any way og validating the availability of any given alias at the time of creation.
Or how do you handle this
Failed the SR if alias already taken
Pause with review activity
or ?
This is not a question about the exchange side this can be for any product where the end user have to choose.
/Kristoffer
0
Best Answer
-
David_Morris1
Member Advanced IT Monkey ✭✭✭
I'd personally do it like this; SR following activities- RB - first Runbook that checks the alias and if available also completes the next activity and assigns the ma below to the requester. and sets the second RB to pending
- MA - Manual activity for user to provide a different alias (completed and bypassed if not required by the above)
- RB - also checks the alias and if already taken sets the MA to pending and the previous RB back to in pending, if the alias is available creates the mailbox
6
Answers
- RB - first Runbook that checks the alias and if available also completes the next activity and assigns the ma below to the requester. and sets the second RB to pending
- MA - Manual activity for user to provide a different alias (completed and bypassed if not required by the above)
- RB - also checks the alias and if already taken sets the MA to pending and the previous RB back to in pending, if the alias is available creates the mailbox
this creates a loop where the ma is placed back into progress and the user has to give a new alias and complete the activity over and over again until they give an available alias.