Perhaps I am just unclear about what is supposed to happen with role completion events, and that doesn't not match what I WANT to happen...

Here is what I hope Role Completion Events would do in Dynamic Forms (and Registration too...) --> The completion event fires each time the condition is correct and adds or updates the Role with its defined expiry date; which I am presuming is calculated as TODAY + EXPIRE DAYS.

SCENARIO

I have a need to add / maintain a role code on certain users based on their answers in a questionaire (DynForm) which, by assigning a valid role code, gives or denies a discount in a completely different module.  I am using the EXIPIRE DAYS to allow them 1 day to use that discount.  If they come back after that, and they again go through the Dynamic Form to get to the other module, they would have to answer the questions correctly again, and thus get their (this time existing) role updated with a new expiry date by virtue of the completion event.

WHAT HAPPENS

On the second time through the form  the program 'sees' the user already has the role and does not fire the completion event. OR perhaps it is using some other date besides TODAY() as the baseline to change the expiry (such as record create date). OR there is a logic I need to understand!

I seem to be the queen (or jester?) of expiry since this is my 3 issue here with them. But then again, they are very powerful and helpful in conjunction with your FABULOUS programs that by and large save my staff DAYS of work on each of our installations!

Please advise, because, as my client says, "registrations are waiting..."

THANKS!!!

David,


Hi. Well we are going to be adding some new functionality to the role completion events however this is how it currently works right now....


Dynamic Role Completion events are the only completion events that fire with a add/remove functionality (we are adding new features to allow you to have it this way, or add only, remove only, etc...) So... What I mean by this is if you have a user response on the event set for the user to answer 'YES' to a question, then if they answer yes the user will be added to the role with the set number of expiry days. If they answer anything other than yes then they would be removed from a role. Unfortunatly once they are added to the role, although the event would fire it would see they were part of that role and not actually add to their expiry days. Right now this is working 'by design' but I can see how more features would help the role event. For example right now many implementations would not want them to be added for more and more days for each submission, however in your case you would... So possibly adding some more features such as 'Always update role expiry days' as a checkbox when setting up the event, or allowing you to set the actual expire date and not just the number of days would also be a great feature to have.


You can do what you are wanting to do now (or almost anything else with User Roles) using a Dynamic SQL Event. There are many threads related to this in the forums so I would just search our forums for 'UserRoles' or 'Insert Into UserRoles' and you will find many threads with scenarios that are either similar or should help your implementation. Even without knowing much SQL you should be able to find enough examples that shouldn't be difficult to implement. We often recommend this for some implementation as well because sometimes you can complete a single SQL Completion event instead of actually setting up many role completion events (we have seen implementations with 100 role completion events ).


If you go the route of a Dynamic SQL Event, you might end up posting your solution here so that other users can benefit from similar implementations down the road.


Thanks for your feedback and questions!


-Chad