"token.tasksSequence" syntax error in the Task Sequence activities

Question

question

David Chan asked Aug 14 2020 at 9:31 AM Phil BoBo commented Aug 18 2020 at 4:13 PM

"token.tasksSequence" syntax error in the Task Sequence activities

Hi dev

There are spelling mistakes in the Task Sequence activities. Some spelled without a "s" after task.

Please check.

David

Software Version:

FlexSim 20.2.0

flexsim 20.2.0 process flow tasksequence

· 5

Mischa Spelt commented · Aug 14 2020 at 9:57 AM

You mean that some are spelled with an s? The thing is called a Task Sequence after all, not a Tasks Sequence.

0 ·

David Chan commented · Aug 15 2020 at 1:10 PM

@phil.bobo

I have enclosed the similar model one is done update 1 and another in update 2. The one in update 2 has an issue as shown below.

exception: Error: Bad Task Executer/Task Sequence reference in starting Task Executer activity "Travel" in process flow "Object"

AGV TS 2020Up1.fsm

AGV TS 2020Up2.fsm

Please advise what was wrong. Thanks

David

0 ·

agv-ts-2020up1.fsm (37.0 KiB)

agv-ts-2020up2.fsm (36.9 KiB)

Phil BoBo ♦♦ David Chan commented · Aug 17 2020 at 10:23 PM

If you open the AGV TS 2020Up1.fsm model in FlexSim 20.2, it runs just fine.

The problem is in the configuration of the first Travel activity in the AGV TS 2020Up2.fsm model.

If you explore its tree, you can see that its resourceRef variable's type is 2. It should be 0.

Up1, type 0 (good):

Up2, type 2 (bad):

I can't figure out how you got this variable to be that value. I can't replicate it getting set to that value erroneously. If you create a new activity, it has the correct 0 value. If you delete the value in the field, then recreate it via typing token.taskSequence or selecting the option Token Label > taskSequence, then it sets the value correctly. If you load the 20.1 model, it has the value set correctly.

I don't know what you did to get this activity to be configured this way. It could be a bug, but without replication steps, we can't confirm or fix it.

0 ·

1597702910101.png (88.9 KiB)

1597702933195.png (90.9 KiB)

David Chan Phil BoBo ♦♦ commented · Aug 18 2020 at 1:23 AM

@phil.bobo

Thanks. I think that is a bug. When you drag out a "Create TS" activity, the next TS activity will have the resourceRef Type at 2. Any other TS activities are ok. On the other hand, if any TS activity is drag out before "Create TS", then it is ok.

Thanks

David

1 ·

1597713615603.png (30.2 KiB)

Show more comments

Answer 1 · 2020-08-14T15:19:01Z

Phil BoBo answered Aug 14 2020 at 3:19 PM tannerp commented Aug 18 2020 at 4:27 PM

I don't see any spelling mistakes in any of the task sequence activities. They are all correctly spelled token.taskSequence.

· 1

question