JodieS

My feedback

  1. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  1 - Nintex Workflow for SharePoint  ·  Flag idea as inappropriate…  ·  Admin →
    JodieS shared this idea  · 
  2. 699 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    To support this requirement we’ve just release the following features

    - Specify a customizable sender display name for both email and task actions, we understand one of the main requests was to be able to supply a custom from email address however due to many of the limitations in the cloud we are currently unable to deliver this request and so hopefully being able to add a From display name will get you one step closer..

    - Add a customizable Reply To email address for the email action so you can control the email address when people hit reply.

    Hope you enjoy these features and be great to hear any feedback once you try them out.

    An error occurred while saving the comment
    JodieS commented  · 

    Although the from Display Name was an improvement, we really need to be able to assign a username e.g. creator/initiator as the sender as others have suggested.

    In our case we are parsing email fields from Nintex/SharePoint O365 into Manage Engine Service Desk Plus, and at present all tickets are being raised against SharePoint Online and not the actual requestor. Consequently the tickets raised cannot send out notifications to the user after creation until a technician has manually updated the Requestor field in MESDP.

    JodieS supported this idea  · 
  3. 64 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JodieS supported this idea  · 
  4. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JodieS supported this idea  · 
  5. 252 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    JodieS supported this idea  · 
  6. 641 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    42 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    JodieS supported this idea  · 
  7. 59 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    JodieS supported this idea  · 
  8. 331 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    JodieS supported this idea  · 
  9. 144 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →
    JodieS supported this idea  · 
  10. 181 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  4 - Nintex Forms for Office 365  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all,

    While this is still in the planned status, we have recently announced a capability that allows you to move your Nintex Workflow for Office365 to Nintex Workflow Cloud. This technology also converts your task forms (Old and New Responsive) to Nintex Workflow Cloud forms. This technology gives you an insight into our conversion capability which we hope to bring to Office365 List Forms in the future.

    Cheers,
    Euan

    JodieS supported this idea  · 
  11. 161 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    JodieS commented  · 

    Agreed - this would be useful, we have an approval workflow for changing shift rosters, and it would be nice when the approval task went to the user to be able to cc their manager in so the manager is aware they have a task to complete.

    An error occurred while saving the comment
    JodieS commented  · 

    We use it in the scenario where the manager logs a request which the employee needs to sign-off before it can go to the next manager for approval. We would like to be able to cc: the creator in when the task is assigned so they can followup if the employee has not responded (in case there is any issues e.g. they didn't receive it, or it went to junk mail etc).

    Also as per other comments, "Bcc is useful for workflow admins during the test phase of a workflow, as you can monitor the workflow in it's early stages to ensure emails are being sent without an impact to business processes."

    JodieS supported this idea  · 
  12. 24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    JodieS commented  · 

    I agree this would be very useful. We currently have a few workflows e.g. Accidents & Injuries, Maintenance requests etc. that require immediate attention if Urgent/Emergency is selected by the user. Being able to flag as high priority would help us improve the response turnaround.

    JodieS supported this idea  · 
  13. 756 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    JodieS commented  · 

    I agree with Maq, Shaunlub & Russ below, Hawkeye is not under the standard licence and I'd be hard pressed to ask for more money to purchase a product just so I can do something that used to be available at no extra charge in on premise versions. Also adding Log to History at every step makes the workflows take a lot longer to run and makes capturing the workflow (e.g. snipping tool) tedious because of the size of the workflow.
    We need to be able to translate each action back in either a text or graphical format so we don't waste hours of time trying to work out where the workflows are falling over.

    An error occurred while saving the comment
    JodieS commented  · 

    If the visual feedback isn’t a possibility, then as Jarrod pointed out below, it would be useful to know at which action the workflow is stopping.
    As a lot of us name each action specifically to know what it is doing, perhaps using the naming of the actions in the feedback along with a more practical response. Eg error occurred at ‘Email CreatedBy’ - email address is incorrect.

    JodieS supported this idea  · 
  14. 307 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JodieS supported this idea  · 
  15. 253 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  3 - Nintex Workflow for Office 365 » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    JodieS commented  · 

    This goes back to the old MOSS 2007 using 'snippets' to recreate common sections of workflow, which works great because you can then make minor changes to them once inserted, as no two workflows are generally identical (e.g. changes to approvers etc.)

    In cases where the duplicate workflows were identical, and you could create one and then call it from another workflow as you suggest above, will it allow you to call the workflow from across sub-sites & other site collections?

    JodieS supported this idea  · 
  16. 19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3 - Nintex Workflow for Office 365  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback, could you please give me a bit more detail about what you are trying to do? Are there particular features that you are looking for? Thanks.

    JodieS supported this idea  · 
  17. 283 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JodieS supported this idea  · 
  18. 228 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    JodieS commented  · 

    The visualization was without a doubt a huge help for fault finding workflows, whereas now we have to add 'Log to History' at every step, making the workflow much larger and difficult to snapshot for records purposes. Especially the colour coding made it very quick to find the specific shape that failed. If we can't have a visual history, then at least a log of each shapes completion would be useful so we didn't have to 'Log to History' within every workflow.

    JodieS supported this idea  · 
  19. 255 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  Jon Hardy responded

    Please have a look at the condition builder just released as part of conditional start. Is this the kind of condition builder that you need in “wait for field change in current item” ?

    JodieS supported this idea  · 
  20. 97 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    At this stage we have no plans to change the validation message location for Classic Forms. We recommend you look at Responsive Forms if you users prefer the validaiton message below the field.

    Once we have shipped Universal Forms for SharePoint, we will revisit the Classic experience.

    Cheers,
    Euan

    JodieS supported this idea  · 
← Previous 1

Feedback and Knowledge Base