TeamDesk Knowledge Base & Support

anjuim moied 2/16/2010 7:15:34 PM

When a number of records need changing at the same time or a record needs updating we can use a rule based on a schedule .It would be nice to have a Manuel trigger so the records could be changed or added instantly .

A tick box for a one off run at the point of saving the new rule, or a button on a view or table that ran the rule.(maybe a url that ran the rule) would be our trigger.

The tick box on a form is ok, but a rule can only run on record change which means the rule will run on check on or off.

I hope this makes sense its very late.

Slava Shinderov  Staff  3/25/2011 3:59:18 AM

@Philipp as workaround you can initiate Workflow Actions following way:

1. Use Customer Button to set an "Email Agent" checkbox in record.
2. Create workflow rule with "Email Agent" is checked filter condition and record change trigger when "Email Agent" column is changed.
4. Create two actions for trigger above: first to send an email and second to assign "false" to "Email Agent" checkbox.

Philipp Matuschka (MMB) 3/25/2011 4:27:39 AM

I'm doing something similar now, but it doesn't take away from the idea of allowing Buttons to initiate Actions. Thanks

Desmond Beatty 9/19/2011 11:40:22 PM

Slava
I am also doing somthing similar in my app. Changing a value in an "interim" field and triggering a workflow rule and action against that. I support Philipp on this one.
Desmond

Arnold Hakobyan 10/16/2011 12:14:20 PM

It won't be better to move the custom buttons into the list of triggers for workflow rules? It could become the forth type of trigger in line with periodic, time dependent ans record change triggers.

Shem Sargent 1/5/2012 4:02:38 PM

I agree with Arnold, this would be a logical place to put the buttons. I would like to see the ability to determine where exactly the buttons show up as well.

Desmond Beatty 9/3/2012 11:20:58 AM

Dear Support

While I am pleased to see this move to "In development", I am concerned to note that this is being prioritized ahead of other workflow requests with a higher score, for example "Workflow Rules - additional actions" score 350 and "Workflow Rules - call URL" score 100 (which is a subset of additional actions in any case).

The real issue for me is that I and other report that we can trigger events from buttons even if a little cumbersome. The lack of "additional actions" is a much bigger constraint.

In short, please prioritize these higher scored, more fundamental requests over the more cosmetic improvement that this case represents.

Comments from other users to this post welcomed.

Kind regards
Desmond Beatty

Slava Shinderov  Staff  9/3/2012 3:03:47 PM

@Desmond while we're listening to our customer feedback, we're not planning system improvements based solely on idea score.

Workflow Rules: Call URL idea definitely on our radar and will be planed for developing soon.

Regarding Workflow Rules: Additional Actions idea, we think that Cascading referential integrity constraints for one-to-many relations is better way to deal with related records at least for delete record action. As for updating related records - we’re not sure that we need to move system in such direction yet. We prefer our current concept with calculating everything on the fly using summary/lookup column instead of updating related records.

The Angel eXchange Admin 9/4/2012 6:32:47 AM

@Slava. Thank you for your response.

I do not expect improvements to be based SOLELY in score. I do expect the reasons behind any given score to be considered, hence my comment to "bigger constraint"

I look forward to the Call URL action as this would enable the triggering of actions external to TeamDesk without the need to poll TeamDesk for changes in records.

Cascading referential integrity constraints are fine for preventing (constraining) the (manual) deletion of parent records. I'm happy with that. However the ability to workflow the deletion of records goes beyond referential integrity. For example, deleting redundant records, such as old timestamp records.

Rick Cogley 9/6/2012 11:52:28 PM

I am glad buttons can directly trigger actions now. We were doing a lot of flag-setting and timestamp-referencing, so this is a positive change for us. Makes life easier, and I look forward to further improvements. Thanks Slava et al!

Arnold Hakobyan 9/7/2012 12:03:48 AM

That's right! Thank you!

Slava Shinderov  Staff  9/7/2012 12:57:55 AM

You can do it now.
Please review Allow Custom Buttons to initiate (Workflow) Actions idea.

Kirill Bondar  Staff  9/7/2012 2:58:28 AM

Merged with:
312 - Manuel trigger for work flow rule.

basenine 9/10/2012 5:18:11 AM

Nice work...
I must have missed this idea earlier because I definitely would have promoted it.... taking it to 110 ;)

Now for the process of changing how my application works!!

Again - nice work!

basenine 11/18/2013 4:35:00 PM

It would be nice to add to the Actions list: Formula URL, rather than creating a column with a Button