Im creating a workflow for approvals using power automate. I also have this reminder system set up to remind them every hour for 4 times and then once a day afterwards. This works when I have a parallel task set up, but for this specific loop in the approval, im using apply to each since i can add as many people to review myd ocument as I want. I notice that I can't reset the delay action while its active because it is still running. The only way it gets reset is that the delay action is finished and starts the loop again and then the variable gets reset.
This works if the loop isnt inside an apply to each and the reminder system works as well.
enter image description here
Related
I'm looking for a way (using SuiteScript 2.0) to handle real-time persistent (stored) field updates, where a field might have changed in NetSuite (for example a lead time was just updated), and it doesn't matter if a user saved the change, or some other automated process changed that field. I just want to be able to pick up on that change:
The moment that it's done, and
Without regard for who or what kicked it off (e.g. it could be a person, but it could also be an automated change from a workflow, or a formula on the field itself which pulls values from another field)
Doing some research I found some options that looked somewhat promising at first. One being the afterSubmit event in a client script, and the other being the fieldChanged event. My issue however is, from what I understood those only really seem to be triggered by a user manually going in and making those changes, but this is only one part of the puzzle and doesn't seem to cover changes made outside of the scope of the user making those changes. Is that correct however? Or would one of those events still be able to capture changes done to that field regardless of who (or what) initiated or triggered the change, and right at the moment the change was saved/ persisted to the database?
UserEvents are basically triggers. In their deployment records you can set the context in which they fire so you can get them to fire in all circumstances (called contexts in Netsuite) but one.
That circumstance is User Events are not fired for record saves made in User Event scripts. i.e., if an AfterSubmit UserEvent script loads, changes and saves your record a fresh user event will not be fired.
Is there a way to trigger an action in Microsoft Flow (Power Automate) when just one specific file in SharePoint gets modified? At the moment I have the situation that 6 files are updated at once, so the same action is triggered 6 times in a row.
I use the trigger "When an item is created or modified". There I can only adjust the SharePoint site name and the list (library) of files to monitor.
Make sure your settings are set in a way the flow don't run in parallel.
In essence, you may want to limit the concurrence of the flow so it will run just once at a time.
1) First go to the settings
2) Limit the paralellism. If you just want to work on the first item then click turn on Split On which will yield a single file.
You can check here for more details.
we have a requirement to delete items from a SP list if they were not modified for 15 minutes.
I configured a simple workflow in SP Designer and assigned it to a change action that pauses for 15 minutes and then deletes the item.
Now, if the item changed while the original workflow is paused, a new workflow will be started (I presume) with a new counter.
But how to terminate the original workflow so that it wouldn't delete the item earlier?
We are on SP2013 on Office365.
Thanks,
I think you can solve it other way.
Use SP 2013 workflow platform, and set the trigger to item creation.
create a date/time variable and set to current date or modified field value
pause wf for 15 minutes
if currentItem:Modified less then or equal your variable stored time
if yes: delete item
in transition to stage section use the 3. step again and if yes: select end the workflow, if no: go to stage one
Only way I can think of is to make the workflow run a Powershell script that has the rights to stop workflows. But keeping track of the workflow instance id and the item is going to be a hazzle.
How about simply putting a check at the end of the workflow that checks if the last modified field is older than 15 minutes. If it is older then delete the item, if it is not then terminate that workflow without action.
Since I don't see the option in schedule properties of an agent, I was wondering if it's possible to run an agent once every 3/6 months, or even every year?
I only see -more than once daily,daily,weekly,monthly,never..
Pick the closest option in schedule properties, eg monthly, and then add code at the beginning of your agent that checks the date and depending on the result either exits without doing anything, or continues running the main body of the code. Works fine with agents written in lotusscript, never tried it with #formula.
I've got a scenario where I want a workflow to not run if a certain condition is true, otherwise to run when a list item is created. The scenario is for a people management system. If a new list item (staff member) is added to the list then the workflows job is to go between the various departments and get everthing setup. Eg payroll, IT account ect. One of the fields is Start Date that may or may not be entered. If it is entered then I don't want the workflow to run when the item is created. I want the policy on the list to start the workflow on that date. I can add some code into the workflow to end itself if the date is in the future but then this will show as completed on the list. This is a problem because the workflow shouldn't show that it's run as in effect it's waiting for the date to be correct.
In other words, is there something in onWorkflowActivated that allows me to stop the workflow from triggering so that nothing shows up in the site, in essence to suppress the workflow from running as if it was never triggered by the OnCreated event.
Can you add a new step at the beginning of the workflow to fill in the Start Date? I think this makes sense in terms of your workflow because the HR person has an action item on their plate: enter the start date.
Otherwise you could make Start Date a required field on the sharepoint list.
This is SharePoint Designer version, see if you can use the same activities in VS
Create a second workflow that executes the rules after StartDate is set
In the main workflow, create a step with the action 'Wait for Field Change in Current Item' and config it to 'StartDate not Empty'.
The next action will be a 'Start Workflow', executing the second Workflow you created.
You also have a Stop Workflow activity