[Amal Vellappillil]

Hi Alex,

Thank you for explaining how things work in SPO.

I have attached the following screenshots.
1. Modified workflow
2. Create Stop variable as Integer
3. CurrentItem Stop as Integer (looking up)

Attachments:

1. 

   Screenshot-workflow-setup-1.jpg
   

2. 

   Screenshot-create-stop-variable-as-int.jpg
   

3. 

   Screenshot-currentitem-stop-as-int.jpg
   

[Amal Vellappillil]

Yes, it seems as if the boolean variable is not getting set with Yes/No values. Rather its getting set with True/False.

In any case I tried creating a an integer variable and setting value from Stop field. I then used that variable and checked if it equals 1. If 1, then stop the workflow. This seem to have worked. You can may be update your documentation to use an Integer variable rather than using a Boolean variable and check for 1. This might be helpful for those who are still in On-Prem SharePoint.

Out of curiosity, what do you use to send future dated emails in SharePoint online?

[Amal Vellappillil]

Hi Alex,

Yes that would work also. However, as you can imagine if we have 20 rules or so, that means we will need another 20 rules to make it work. Its better to use customJS at that point to check if the value changed based on the ruleID and triggerField.

Do you think this can be a feature added to a future release? A new operator or a checkbox next to the operator dropdown asking “is changed from initial value”? I think it will help.

Thank you for taking the time to provide a solution.

-Amal Vellappillil

• This reply was modified 3 years, 11 months ago by Amal Vellappillil.

[Amal Vellappillil]

Glad you are able to look into this and possibly skip duplicate calls to presaveaction method. It would be nice if the library could handle the logic than users remembering the little quirk and do the workaround on each and every form.

[Amal Vellappillil]

Sounds good to me 🙂

[Amal Vellappillil]

Hi Alex,

I have a suggestion/enhancement request. I noticed that it would be very helpful to have all the field names available as intellisense in Ace editor. So I added this to your “aceAutocomplete” function inside DFFS_backend js file.

var fieldNamesCompleter = {
                    getCompletions: function(editor, session, pos, prefix, callback) {
                        var wordList = spjs.dffs.data.listFieldsArr.map((f) => f.fin + "|" + f.disp + "|" + f.type); 
                        callback(null, wordList.map((word) => {
                            var wordArr = word.split("|");
                            return {
                                caption: wordArr[1] + " - " + wordArr[2],
                                value: wordArr[0],
                                meta: "listField"
                            };
                        }));
                
                    }
                }
                a.completers.push(fieldNamesCompleter);

This code was added inside the else block where you are setting enableBasicAutocompletion: true. You can use this as is or modify to your willing to adapt to your coding styles. I hope this gets added to the future versions of DFFS.

Thank you,
Amal Vellappillil

[Amal Vellappillil]

So I put debugger at the top of the presaveaction function and sure enough it got hit twice. So I still dont understand what is causing it to be called twice, but the workaround you mentioned skips the item creation the second time around.

Thank you so much for the workaround and tips on debugging.

[Amal Vellappillil]

Hi Alex,

Thank you for the quick turn around. I will give it a go.

– Amal Vellappillil

[Amal Vellappillil]

Hi Alex,

That would be awesome!

Thank you,
Amal Vellappillil

[Amal Vellappillil]

See attachment below. Hope it helps.

Attachments:

1. 

   create_new_rule_from_clipboard_data.jpg
   

[Amal Vellappillil]

try this

{ReleaseDate['MMMM dd, yyyy']}

[Amal Vellappillil]

Thank you for taking the time to explain the difference.

[Amal Vellappillil]

Hi Alex,

Thank you so much for the snippet.
Just out of curiosity. What is the difference between the way you have it vs comparing between beforeProperties and getFieldValue?

spjs.dffs.beforeProperties[fin] !== getFieldValue(fin)

-Amal Vellappillil

[Amal Vellappillil]

Hi Alex,

Thank you for getting back so quickly. I will use this workaround till a proper fix is released.

Thank you,
Amal Vellappillil

[Amal Vellappillil]

Awesome. Thank you so much for all the clarifications and directions.

Stay safe.

[Author]

Posts