You’re trying to pass the current time via the Trigger Workflow step? Can you use a Template column to hold the current time in the workflow triggered by the Manual trigger?
1 Like
Not soon as workflows run like an “Admin” user and not a specific user. The workflow cannot reference a user-specific column because it doesn’t know which user you are referencing
You could reference values in the Users table though if that helps you. You could filter for the User in the Users table based on who pressed a button
1 Like
Yeah, that’s a good workaround for the server side workflows. The client side “App interaction” would require a “Now” column in the User table. There are workarounds, but I’ve been spoiled in selecting the current time in the menus. 
The only use case that I’ve thought of is where it would be important to capture the time the user presses the button and not when the workflow ran at GMT. 
All great stuff @DJP !!
When are you planning on flipping the switch to let us all to have such nice neat workflows in folders?!!
I’m pretty sure workflow folders have been available to everyone for a while now. Just need to name your workflows with a forward slash Folder/Workflow.
5 Likes
Amazing, thanks!
1 Like
Tell me what the problem might be related to, I change the user’s Role through Manual Workflow. It is installed normally, but after some time it takes and changes back, has anyone else encountered this problem?
This is documented behaviour:
To change a users role, you have 3 options:
- Do it manually in the Data Editor
- Use the Glide API
- Use a server-side workflow.
You probably misunderstood me, I use option 3. The problem is that I notice more than once the behavior that the role returns after some period of time
For example: You have a user role, and today I set the Admin role for you, but tomorrow I notice that the user role has been returned to you.
Are you 100% sure you are using a server side workflow, and not a client side workflow?
Can you show me the workflow configuration?
Okay, couple of things.
Firstly, it appears that you are targeting the User Rows incorrectly. Instead of targeting the Loop, you should be targeting Loop->Current row, like below:
Secondly, where are you getting the value from for the Set Column Values?
As far as I can see, you are taking the current Role from the first row in your table, and writing it back into the same column.
I just tested this, and it works as expected (and the values persist after a refresh).
2 Likes
Maybe my English is not translated correctly, I have no problems with Workflow, it works correctly.
- If you set 1 cycles in Loop, then always one row is returned and you do not need to select Current Row
- I get the value from Form Screen
I think this is related to the problem with caching PWA applications. And therefore the previous role is returned to the user.
In any case, thank you.
Okay, I see.
So like I said, it works as expected when I test it, so I can’t explain why it doesn’t work for you.
My terrible English is misleading you. I didn’t say that it doesn’t work for me. I SAY EVERYTHING WORKS FOR ME.
But there is a but, after an indefinite time or indefinite circumstances the previous role returns.
Yes, I understand. That’s why I initially thought you might be using a client side workflow, because that would be the expected behaviour.
I’ll check back in my test App after a few hours to see if anything has changed. If the values do indeed revert, then I’d say that’s definitely a bug.
The important part is to use a PWA app for testing.
For my part, I will also try to catch this error to prove that it happens.
1 Like
Can you send me the URL of your workflow?