How to dynamically implement milestone bar?

RE: How to dynamically implement milestone bar?

varunkumarb0001 — Wed, 13 May 2020 13:43:48 GMT

haha... very true

RE: How to dynamically implement milestone bar?

varunkumarb0001 — Wed, 13 May 2020 13:41:59 GMT

Thanks Vimal, that reject fix worked.

RE: How to dynamically implement milestone bar?

Mike Schmitt — Wed, 13 May 2020 13:38:34 GMT

that should work, though i'd consider that more of a workaround than actually fixing stuff that could probably be fixed by cleaning up the internal code 😉

RE: How to dynamically implement milestone bar?

vimalkumars — Wed, 13 May 2020 13:33:06 GMT

Hi Varun Kumar,

Using the reject function to remove the null values from the milestone list can be useful

Can you try the below code?

a!milestoneField(
  active: - 1,
  steps: reject(
    rule!OSR_RULE_General_APN_isValueBlank,
    {
      index(
        local!statuses[1],
        /* Handling Pending */
        "StatusTypeName",
        {}
      ),
      if(
        not(
          rule!OSR_RULE_General_APN_isValueBlank(
            local!acceptedBy
          )
        ),
        index(
          local!statuses[2],
          /* Handling Approved */
          "StatusTypeName",
          {}
        ),
        {}
      ),
      if(
        tointeger(
          local!statusTypeID
        ) = 5,
        index(
          local!statuses[3],
          /* Handling Ordered */
          "StatusTypeName",
          {}
        ),
        {}
      ),
      cons!OSR_TEXT_STATUS_CANCELED
    }
  )
)

RE: How to dynamically implement milestone bar?

Mike Schmitt — Wed, 13 May 2020 13:23:33 GMT

I don't think your code is overtly wrong. It looks like there's a bit of buggy behavior where index() is returning a value of null() when the named property isn't found, instead of the "default return value"... at least when pointing at a local variable.

I think you need to rewrite the code where you refer to local!statuses[index] -- if the status array will always be basically the same, you could probably just write local!statuses[3].StatusTypeName, for example.

RE: How to dynamically implement milestone bar?

varunkumarb0001 — Wed, 13 May 2020 13:16:22 GMT

Didn't get you David. Can you please elaborate what can be vice versa in the code?

RE: How to dynamically implement milestone bar?

davel001150 — Wed, 13 May 2020 13:09:02 GMT

It could possibly be vice versa, too.

RE: How to dynamically implement milestone bar?

varunkumarb0001 — Wed, 13 May 2020 13:08:12 GMT

a!milestoneField(
      active: - 1,
      steps: {
        index(
          local!statuses[1], /* Handling Pending */
          "StatusTypeName",
          {}
        ),
        if(
          not(rule!OSR_RULE_General_APN_isValueBlank(local!acceptedBy)),
          index(
            local!statuses[2], /* Handling Approved */
            "StatusTypeName",
            {}
          ),
          {}
        ),
        if(
          tointeger(
            local!statusTypeID
          ) = 5,
          index(
            local!statuses[3], /* Handling Ordered */
            "StatusTypeName",
            {}
          ),
          {}
        ),
        cons!OSR_TEXT_STATUS_CANCELED
      }
    )

That's the code snippet, I'm using.

RE: How to dynamically implement milestone bar?

Mike Schmitt — Wed, 13 May 2020 13:04:04 GMT

I can't be 100% sure without seeing your code, but my guess is you've used a "null()" somewhere instead of an empty set ("{}") - which would create a "blank" entry on the milestone bar instead of ignoring that position.

RE: How to dynamically implement milestone bar?

varunkumarb0001 — Wed, 13 May 2020 12:47:13 GMT

Thanks . That worked well. But there's a little UI glitch I'm getting, it's creating extra space for null value.

You can see there's extra space between "Approved" and "Canceled" for local!isOrdered as false. Any way to handle this extra space.

Thanks

Screenshot attached.

RE: How to dynamically implement milestone bar?

Mike Schmitt — Tue, 12 May 2020 18:47:21 GMT

The logic might get a bit complicated but you should be able to handle this using if() conditionality in the code determining the "Steps" and "Active" parameters in your milestone field. I'll attempt some brief pseudocode below to give a starting point for how you can do the logic tree:

if(
  not(local!isCancelled),  /* any boolean value registering whether order was cancelled */
  
  /* non-cancelled logic: */
  a!milestoneField(
    steps: /* regular steps */
    active: /* current step */
  ),
  
  /* cancelled logic: */
  a!milestoneField(
    active: -1, /* shows all steps as completed */
    steps: {
      "Pending",
      if(local!isApproved, "Approved", {}),  /* show an entry for "approved" only if approved */
      if(local!isOrdered, "Ordered", {}), /* show an entry for "ordered" only if it was ordered */
      "Cancelled"
    }
  )
)