David cross
My feedback
-
209 votesStarted · 14 comments · 5 - Nintex Workflow Cloud » Dashboard Experience · Flag idea as inappropriate… · Admin →David cross
supported this idea
·
-
44 votesUnder Review · 3 comments · 5 - Nintex Workflow Cloud » Connectors · Flag idea as inappropriate… · Admin →David cross
supported this idea
·
An error occurred while saving the comment -
26 votes1 comment · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanAn error occurred while saving the comment David cross
commented
What would be the use case for this? In workflows I use the regex feature for something similar and it works. And in case someone else is struggling with an idea for your use case, I use this in a workflow for the following purpose:
I have a document library that contains tax certificates. We have a specific naming convention when the files are uploaded to the doc library.
The file format is 10-digit customer ID, underscore, 8-digit effective date (YYYYMMDD), underscore, 8-digit expiration date (YYYYMMDD), underscore, 1-character certificate type code, underscore followed by the state(s) the certificate is applicable.
I use the regex feature to parse out the customer ID, effective and expiration dates an the certificate type. The workflow then moves the file to a folder with the expiration year and then sets the metadata fields corresponding to the Customer ID, Effective Date, Expiration Date and Cert Type.
If the filename doesn't conform to the regex, it sends an e-mail to the person who uploaded the file to check the file name for errors.
This has freed up lots of time for our tax department as they just need to drag and drop the certificates into the root of the document library and the workflow does the rest.
-
34 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanDavid cross
supported this idea
·
-
53 votes2 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →
Thanks for your suggestion. I will update this ticket if the status changes.
Cheers,
EuanDavid cross
supported this idea
·
-
75 votes
There are no updates on this idea at this time. If there is anything to share, I will update this idea.
Cheers,
EuanDavid cross
supported this idea
·
-
138 votes12 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →
Hi all,
This is still in the backlog to be done but it is not scheduled. When this is scheduled, I will update the status.
Cheers,
EuanDavid cross
supported this idea
·
-
19 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanDavid cross
supported this idea
·
-
9 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →David cross
supported this idea
·
-
4 votesDavid cross
shared this idea
·
-
29 votesDavid cross
supported this idea
·
-
674 votes48 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Hey all,
There looks to be 2 requests here
- Update Inline function to allow calculate date difference, factoring in only business days / hours
- Update Calculate date action to factor in only business days / hours
Can you please share which of the two you require and your use cases
Thanks
LisaDavid cross
supported this idea
·
An error occurred while saving the comment David cross
commented
For me, it would be great if the "Add Time to Date" action had the ability to choose between the calendar and business options as well. I use the Add Time to Date function to set the due date for tasks. This would make it easy to set a due date that is three days from the current date and if I define my business days on my site as Monday through Friday, a task created on Thursday would be due on Tuesday rather than Sunday.
Since this option is available in task escalations, it should not be too hard to implement I would think. However, it would be nice if you could calculate a due date directly in the task actions instead of having to use a separate "Add Time to Date" action to set a workflow variable as the due date.
-
Support lists with versioning turned on and where "Append Changes to Existing Text" is set to "Yes."
373 votes46 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →Hi all,
There is no movement on this feature at this time. If the status changes, I will update this ticket.
Cheers,
EuanDavid cross
supported this idea
·
-
25 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanDavid cross
shared this idea
·
-
108 votes6 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →David cross
supported this idea
·
-
239 votes24 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion Scott. We are soon to begin building the List Lookup control for Universal Forms and will put this into consideration when building the new control.
Cheers,
EuanDavid cross
supported this idea
·
-
310 votes19 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Hi all,
We will soon begin the development of the List Lookup control for Universal Forms and take this feature request under consideration.
Cheers,
EuanDavid cross
supported this idea
·
There should also be a way to export the items in the Tasks view in NWC to Excel or a csv file. This would help with auditing requests.