elsa | Java serialization , faster and space efficient version | Serialization library

Use remove_unused_levels:

From the documentation:

Unused level(s) means levels that are not expressed in the labels. The resulting MultiIndex will have the same outward appearance, meaning the same .values and ordering. It will also be .equals() to the original.

If I understand correctly, your activity is responsible for loading in the data and looping over it, while the user of the activity should be able to specify what happens in each iteration.

If so, then you might implement something like this:

If you're just getting started with Elsa, then please make sure to use Elsa 2, since Elsa 1 isn't supported anymore.

With Elsa 2, you can define your activity input as follows:

You can make SimpleMovieItem object Parcelable, and when you click one item, you can create an Intent that put your SimpleMovieItem object to the bundle extra of your intent:

The tidyr::nest() does this directly. Notice for each combination of grouping/nesting variables, a tibble is neatly tucked into the data cell. I've modified your function a little by (a) removing the aspects unrelated to grouping (like filter) and (b) making groups default to an empty character vector so if nothing is passed then nothing is grouped.

Also, the names (e.g., male honors) are easily retrievable via variable values. That's typically a lot more useful than retrieving the values from the variable names.

Will this work for your purposes?

Most likely the issue is that the docker image for the dashboard is not compatible with the workflow server hosted by your application.

The cause of this mismatch is that the blog post references Elsa 2.3 NuGet packages, while the dashboard docker image is built from the latest source code in the master branch (which is something that should be fixed to avoid confusion like you're experiencing).

To make the dashboard work (which is built against latest source code), you need to update your workflow server app to reference the latest Elsa preview packages from MyGet (which are also built against latest source code from the master branch).

The following documentation describes how to reference the MyGet feed: https://elsa-workflows.github.io/elsa-core/docs/next/installation/installing-feeds#myget

First of all, you have to understand how elsa loading context work.

when you enter the type of your workflow context it automatically make loading for your workflow Context with null value in context Id.

so you can not access your Workflow Context so what should you do?

you have first to access your HTTP Endpoint body to get your the information that you want.

using JS syntax

Try this:

It looks like you trying to implement some kind of machine-to-machine interaction.
In this case you can consider using client credentials flow instead of authorization code flow which you are currently using.
That means you need to add another client into IdentityServer4 config with corresponding settings. And then instead of passing your frontend's accessToken everywhere you start using new IdentityServer client, server-side one in this particular case.

Talking about disadvantages. Well, most likely you need some information about current user and your new server-side accessToken won't have such kind of details inside (because it's not a user who is starting a process here, but a service).
In this case I might suggest adding another method or controller with some new parameters like userId, for example. This method or controller can be made accessible from only specified IdentiyServer4 clients through policies.