I am looking for a way to activate the Process Model as soon as a user opens the record summary for the first time.
Additionally, I want to record the time when the summary was first accessed.
Is there any way to achieve this?
One possible solution that I thought of is displaying a button to start the process model when the summary interface is launched.
Discussion posts and replies are publicly visible
For what purpose?
Hello tejas_n
How is this user going to open the summary? May be simply open this summary by a process if that is what you really want and write down the data if that is the first entry for that identifier.
But why?
We want to capture the date and time when the user opened the case form record read-only grid as per business criteria rules will send out notifications and other things.
when the user clicks on the record link (dynamic links /record link on read-only grid ) we cant start the process model as per my analysis
So is any way to start process models when the user open interfaces at load
In that case, you can have your summary interface designed in such a way that it triggers a process model and then displays the summary of the record.
On the first click your interface would check on the entry in the data base for that particular record, if exists it would show summary else it would show the button first on the interface which says "Click to View Summary" which would trigger a process and save a value into the local and display the summary.
an expression rule, contains to check the data and display the summary will fulfill your requirement.
I am not sure whether this will pass any UX test ...
Wasn't sure of any other approach, how that requirement could be fulfilled. Definitely not a preferred approach.
then it sounds like you don't want to use records and instead have people "think" they are accessing records by starting a process to get a task that is the summary page instead....not sure I would recommend this as you add overhead to the platform and to O&M and lose some basic value of recordsI would double click into the requirements and try to get to business need of some of this - are you sure you are solving for the right thing the right way.Just food for thought
Konduru Chaitanya
Yes thought of this approach is best for now
But trying to minimise the clicks of user not to add like click to view record on the interface
ChristineH Yes the process model approach is also a way by using the activity chaining
Bt its now the best for resources
Thankyou you all
Stefan Helzle
ChristineH
Hi Tejas,
Can you help with below questions.
1. Does use perform Any action after click? 2. If this is just for readonly , any specific reason the process model needs to be triggered?
3. Once the summary interface is launched, any specifc reason to use button instead of related action?
Though this is not a right solution, this needs to be customised as per your requirement, build a grid which is similar to record summary view and on click of the link use starprocess link and start the process.
karthikkanjerla
1. The user can see the summary screen and other related actions on the record2. As mentioned we need to capture the record that has been opened.
tejas_n said:We want to capture the date and time when the user opened the case form record read-only grid as per business criteria rules will send out notifications and other things.
3. As related action will be done by a user we can't fully rely on them if they don't use related action
we have to force the user to click the button and capture the time before they see the record
if the user opens and doesn't click related action to capture time (this will break the use case )
karthikkanjerla said:Though this is not a right solution, this needs to be customised as per your requirement, build a grid which is similar to record summary view and on click of the link use starprocess link and start the process.
Yes this is not the better solution as it will consume resources of appian
tejas_n said:But trying to minimise the clicks of user not to add like click to view record on the interface