[Alexander Bautz]

There is currently not a “between” operator, but you can try setting up two rules – one for “is less than” and one for “is greater than”. For the first you set no “actions” and for the second one you add the previous rule index in the field “And these indexes are true”.

Alexander

[Alexander Bautz]

This sounds strange. Can you verify that you can set the value in a text field? – are you sure this rule is triggered?

Alexander

[Alexander Bautz]

There is not a definitive limit, but 100 rules will take its toll on the browser. I have not tried this myself though.

Your specific requirement would be better solved with a few lines of custom JS. This will require a list of the fields you want to apply this rule to, and a corresponding list of comment fields to make required.

I’ll try to whip up an example during the weekend.

Alexander

[Alexander Bautz]

Hi,
The “hide in child NewForm” option was initially intended for NewForms where you did not have any other code to handle the hiding of the field. DFFS ignores this setting and will make this field visible again if the field is included in a tab or made visible by a rule.

I’ll see what I can do to make DFFS respect this setting.

Alexander

[Alexander Bautz]

Hi,
It should be enough to have the variable “spjs_dffs_license” (or “spjs_license”) in the page where you configure DFFS.

Alexander

[Alexander Bautz]

Hi,
This is not built in functionality as JavaScript cannot send an email on it’s own. I think your easiest solution is to create a workflow that starts when a field is set to a certain value / changed, and then use a DFFS rule to set this field based on a condition.

Another option is to use this solution: https://spjsblog.com/2010/06/16/send-email-with-javascript-with-the-help-of-a-workflow-in-a-dedicated-send-email-list/ and call a function from the custom js section in the misc tab with a rule in DFFS.

Alexander

[Alexander Bautz]

Yes, this should be straight forward – did you test it?

Alexander

[Alexander Bautz]

Hi,
I’m not sure I can do anything about this as by default there is a redirect / refresh when deleting an item or closing a dialog. If you do not have a “Source=SomeURL” in the URL, you will be redirected back to the default list view of the list you deleted the item in.

You might be able to “hack it”, but this would take some custom code.

As a start you can look at this code that hijacks the built in delete function in SP2013 and possibly SP2010? (add it to the DispForm of the item you want to delete):

/* must refer jQuery and spjs-utility.js scripts */
DeleteItemConfirmation = function(){
if(confirm("Are you sure you want to delete this item?")){
var res = spjs_deleteItem({"listName":_spPageContextInfo.pageListId,"id":GetUrlKeyValue("ID")});
if(res.success){
if(GetUrlKeyValue("IsDlg")==="1"){
alert("Item deleted successfully");
window.frameElement.commitPopup(); // < this code will make the parent page refresh...
}else{
alert("add a redirect here..:");
}
}else{
alert("Delete failed with this message:\n"+res.errorText);
}
}
}

Alexander

[Alexander Bautz]

Hi,
I have released DFFS frontend v4.103 – look at the change log here: https://spjsblog.com/dffs/dffs-change-log/

This relase adds a class “dffs_required” to the

of all required fields. You can use this to add your custom style to required fields. Look at the bottom of the file DFFS_frontend.css for an example.

Alexander

[Alexander Bautz]

Hi,
Yes, it’s your HTML. You cannot add a <tr> like this as it is not appended to the table directly, but added in a <td> within another <tr>.

This means you end up with invalid HTML and the browser will try to fix it – resulting in this strange behavior.

I’m not sure what you want to achieve here, but if you add an “empty” heading, this is what the HTML looks like:

<tr id="heading_66" style="display: table-row; cursor: default;" fieldtype="dffs_heading"><td class="tabH1" colspan="2"><div></div></td></tr>

where “66” is the heading ID I added in the “Unique ID” field for the heading.

Alexander

[Alexander Bautz]

I will add a class to required fields when I fix a bug in setting fields not visible in the current tab to required (this produces multiple red stars).

Alexander

[Alexander Bautz]

Hi,
This looks strange. I’m not sure, but it may be problems using this solution if you have “publishing features” turned on as adding a CEWP to such a page may result in strange behavior.

Unfortunately I don’t have a solution to this on the top of my head.

Alexander

[Alexander Bautz]

This is currently not possible, but I will try to get this in the next release.

Alexander

[Alexander Bautz]

Hi,
The gradient.png file was used in the CSS file in v3 and is actually in the v4 CSS file as well, but I forgot to include this file in the v4 packeage.

I am about to release an updated version of DFFS later tonight, and have decided to removed the file reference from the CSS file.

Alexander

[Alexander Bautz]

Hi,
I have made some changes to the DFFS_backend.js file to use “GetGroupCollectionFromSite” instead of “GetGroupCollectionFromWeb”. This will pull all the user groups from the site collection and not only from the current web.

I’m afraid you cannot have the DFFS_backend in another site collection as this will pull the wrong user groups.

I will publish this updated version later this weekend.

Alexander

[Author]

Posts