K Mikesell

My feedback

  1. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    K Mikesell supported this idea  · 
  2. 5 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
    K Mikesell commented  · 

    I think a 'Sleep action' is what is needed here. Keep the thread, but sleep; this would avoid the SQL Update conflicts that occur during a race condition. Assume sleep would be less than a minute.

  3. 267 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    K Mikesell supported this idea  · 
  4. 235 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
    K Mikesell commented  · 

    Need Base64 Encode/Decode action. This is necessary to send JSON message via url querystring as Base64 string.

  5. 410 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

    Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.

    To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.

    An error occurred while saving the comment
    K Mikesell commented  · 

    When using Site Collection Reusable workflow it is not possible to run on condition, so it would be necessary to know the previous field value. Cannot use conditional start. If version history is enabled on listitem you have all of the previous values.

    K Mikesell supported this idea  · 
  6. 476 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    The task ID is populated once the task is completed. Before this the task list items can be locked by the task engine for processing and a workflow accessing this task may fail. There has been therefore a strong reservation form our Engineering group to implement this capability even if technically feasible.

    If one wishes to delegate the task then the delegation should be used.

    Should you have other use cases for accessing the task list before the task is completed then please let us know what they are. There may be an alternative way of meeting this need that will not introduce the possibility of workflow failure.

    K Mikesell supported this idea  · 

Feedback and Knowledge Base