majestic | A lightweight website built for Made By Mirac | Frontend Framework library

Nowhere in your code do you attempt to print the word. How did you expect it to appear in the output? If you want the word, put it in the list of things to print:

give this pipeline a shot. if that's not the expected result, let me know the exact shape of the output you need.

The MatTableDataSource accepts an array not an object.

You have to set:

It looks like you are using jQuery already. You might want to consider using the toggle() function, which is just for this purpose:

https://www.w3schools.com/jquery/eff_toggle.asp

Your first diagram assumes that the duration of logging is always shorter than processing:

• If this assumption is correct, the upper flow reaches the flow-final node, and the remaining flows continue until the first reaches the activity-final node. Here, the processing continues and the activity ends when the processing ends. This is exactly what you want.
• But if once, the execution would deviate from this assumption and logging would get delayed for any reason, then the end of the processing would reach the activity-final node, resulting in the immediate interruption of all other ongoing activities. So logging would not complete. Maybe it’s not a problem for you, but in most cases audit expects logs to be complete.

You may be interested in a safer way that would be to add a join node:

The advantage is that the activity does not depend on any assumptions. It will always work:

• whenever the logging is faster, the token on that flow will wait at the join node, and as soon as process is finished the activity (safely) the join can happen and the outgoing token reaches the end. This is exactly what you currently expect.
• if the logging is exceptionally slower, no problem: the processing will be over, but the activity will wait for the logging to be completed.

This robust notation makes logging like Schroedinger's cat in its box: we don't have to know what activity is longer or shorter. At the end of the activity, both actions are completed.

Activity diagrams are not really meant to express timing and duration. It's about the flow of control and the synchronization.

However, if time is important to you, you could:

• visually make one activity shorter than the other. This is super-ambiguous and absolute meaningless from a formal UML point of view. But it's intuitive when readers see the parallel flow (a kind of sublminal communication ;-) ) .
• add a comment note to express your assumption in plain English. This has the advantage of being very clear an unambiguous.
• using UML duration constraints. This is often used in timing diagram, sometimes in sequence diagrams, but in general not in activity diagrams (personally I have never seen it, but UML specs doesn't exclude it either).

Time is something very general in the UML specs, and defined independently of the diagram. For example:

8.4.4.2: A Duration is a value of relative time given in an implementation specific textual format. Often a Duration is a non- negative integer expression representing the number of “time ticks” which may elapse during this duration.

8.5.1: An Interval is a range between two values, primarily for use in Constraints that assert that some other Element has a value in the given range. Intervals can be defined for any type of value, but they are especially useful for time and duration values as part of corresponding TimeConstraints and DurationConstraints.

In your case you have a duration observation for the processing (e.g. d), and a duration constraint for the logging (e.g. 0..d).

8.5.4.2: An IntervalConstraint is shown as an annotation of its constrainedElement. The general notation for Constraints may be used for an IntervalConstraint, with the specification Interval denoted textually (...).

Unfortunately little more is said. The only graphical examples are for messages in sequence diagrams (Fig 8.5 and 17.5) and for timing diagrams (Fig 17.28 to 17.30). Nevertheless, the notation could be extrapolated for activity diagrams, but it would be so unusal that I'd rather recommend the comment note.

but in the JavaScript code, we simply do not call the setUserName() function, instead, it runs through a conditional statement (if-else) (as followed through the tutorial).

But you do call it:

You are accessing the object Animals from the json so you should change it to:

foreach ($animals[0]->Animals as $animal) {

Q: Is there a better way to do this or fix this?

A: Yes:

You can access it like this