Jump to content

Miro

Hornbill Developer
  • Posts

    240
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Miro

  1. Hi @Paul Alexander

    There is no such option available at the moment. This kind of problem where value of one field is dependent on value of other is quite complex.
    It's similar to having value 5 in A and wanted to have in B minimum A+10 or in C double that - there could be much more examples like this one.

    Solving this with adding specific code per scenario is not a way to go, will think what could be other choices but definitely there is no easy way.

    Thanks,
    Miro

  2. @Paul Alexander I think I replicated problem, it is allowing to click because when new field is added (it become visible) there is missing evaluation of form status - and as new field is mandatory the form is invalid now. It work only when you modify value of new field.

    Let me work on proper fix for it. Will notify you about fix status here.

  3. Hi @chriscorcoran,

    You can see activities in all the cases below:
    - is assigned to you, group your belong to or shared role,
    - created by you (as an owner),
    - your coworker activities if you are set as a manager in their profile (until they mark activity as private).

    All that cases grants you right to open and see task data. This was done since beginning and as far as I know nothing changed here.

    Thank you,
    Miro

  4. Thanks @Edward Melconian for quick respond. Indeed in your post there is no custom fields payload. 

    Could you check if your instance has this flag set on: experimental.feature.bpm.allowcustomtaskfields

    Here you have a full xmlmc payload for complete task call: 
    <methodCall service="task" method="taskComplete" csrf_token="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"><params><taskId>TSK20181112000007</taskId><outcome>Completed</outcome><timeSpent>2880</timeSpent><details></details><taskAnswers><key>somefield</key><value>test</value><displayValue>test</displayValue></taskAnswers></params></methodCall>

    Anyway, will have a look again as I can't replicate your problem even if I replace my customFields with yours.

  5. hi @Edward Melconian

    I used your xml "customFields" in my test task and was able to complete task without any problems.

    The best option will be to do following 3 steps:
    1)    click on task and see what is being return from server,
    2)    complete task and see what is send back to server,
    3)    click on task again and see what is being return from server

    This will allow me to see what is missing.

    Here is a simple screenshot showing in CHROME how to make step 1 & 3:

    image.png

     

    And what to check in step 2:

    image.png

     

    If you can do step above it will speed up things a lot as I should have enough info to see at what stage problem appear. Crucial here will be to see what is being send to server in step 2 and then what is being return in step 3.
    Also If you can paste results like I did - as screenshots (or if you don't want here then send it via private message).

    Hopefully it should be enough to make some progress with this issue.

    Thank you,
    Miro
     

     

     

     

  6. hi @Edward Melconian

    I'm looking right now at your taskGetInfo result and can't see there taskAnswers tag - should be there if task was containing custom questions and is completed.

    Could you create again task with custom question(s) and see what is being send to server when you complete it? I'm interested to see if there is any <taskAnswer> tag (should contain strings similar to this one <taskAnswers><key>field_1</key><value>test</value><displayValue>test</displayValue></taskAnswers>).
    Please also mention me when you answer.

    Miro

  7. @Alisha finally! B) 
    At the moment there is a limitation with pro capture were it should not start with branch and unfortunately we have this situation. You had twice request category so it's been removed from second flow. This cause that flow looks like:

    ... Preferred Contact -> Request category ->  SWITCH -> BRANCH -> SWITCH -> 3rd flow...

    In red "Switch -> Branch" represents second flow that has no form at the beginning because it was automatically removed (found doubled). So solution was to remove request category from first flow and this change flow to be split like this:

    ... Preferred Contact -> SWITCH -> Request category ->  BRANCH -> SWITCH -> 3rd flow...

    Anyway glad that I can help and sorry that it took so much time but it wasn't easy to find it. Pro capture can be done in so many different configurations...

×
×
  • Create New...