Camunda 1 to n - modify multi instance subprocess at runtime - bpmn

I have a specific requirement in 1 to n problem. If I have groups and in each group there are multiple items, then I can give these groups to multi instance subprocess.
If a group is not completed because of an issue in one item, then I want to remove that item out of that group and finish processing that group. Is this addressed in 1 to n problem. If yes, what is the solution for this?

Related

Surrounding Events in KQL or Matching on Multiple Conditions

Coming from a ELK background, Kibana had some nice functionality where you could view surrounding events of any record you wished https://www.elastic.co/guide/en/kibana/current/discover-document-context.html, i.e. view the 5 preceding and 5 proceeding events.
Does something like this exist in the Kusto Query Language?
Edit: I should also mention the requirement for this as I realise it might exist, but within a different form.
I'm looking to find several events that need to have all occurred during a specific time period, i.e. the previous 5 minutes.
Example; if EventID's 1, 2 and 3 show, I'm not interested. However, if 1, 2, 3 and 4 show (within X minutes of each other) then I would like my query to pick this up.
Any hints or tips are appreciated.
It seems that Time Window Join is what I needed - https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/join-timewindow

how to delete n rows in spring data rest

i'm trying to delete n rows from database and n is variable should be given in the api method like deleting the last 10 boxes of items in supermarket which means they are sold so how i would do so i'm using spring data rest i don't know how to write the query in the repository and how i would get the variable n and use it in the sql query also i should check if that number of rows exist before deleting

Task Management Script (1 database of tasks all users must complete indipendantly)?

Explanation: I currently have a database of thousands of tasks and a few hundred people that can see these tasks. Each user has their own login but all see the same list of tasks and all have to complete all of these tasks.
My Problem: I want each user to be able to mark each task complete as completed within their account without marking it complete for all other users.
What I currently have: 1 table of tasks and descriptions, 1 table of users, 1 table of discussion on each task. Users can login and see all of the tasks but cannot mark them complete.
I'm not sure if I am explaining this well enough but I am just looking for any insight as to the best way to get started with this as I kind of hit a brick wall and need people smarter than me to give their insights :)
Thank you all in advance for your comments.
You need one more table that holds the relation between the users and the task.
Everytime a user completes a task you make an entry into that table:
idx task_id user_id
1 1 3
2 4 3
3 1 5 ...
That way you can query for users who have completed a task, or the tasks completed by a user, the tasks that have not been completed by a user, etc...

Run jBehave story n number of times

I have a jBehave/Selenium story which has certain steps (e.g. to create a record)
Now I want the same steps to be run n number of times (i.e. i want to create n records)
How can I do that in jBehave?
I am using Selenium WebDriver.
I think the normal way to execute the steps in a story n number of times is to have an examples table containing n rows: http://jbehave.org/reference/stable/story-syntax.html.
Another solution might be to have a step "When n records are created". The implementation of this step just calls the code of the steps needed for the creation of a record n times.

Running multiple Thread Groups sequentially in JMeter

I have a Test plan in which there are multiple Thread Groups.
I want to run all of the Thread Groups sequentially.
Thread Groups are as below:
Thread Group1
Thread Group2
Thread Group3
. . .
Thread GroupN
I've read in different blogs and articles on the internet, people claiming that the thread groups will run in the order they are defined but apparently they are not in my case. Thread Group4 runs before Thread Group1. Thread Group4 is generating a report which is wrong because it runs before Thread Group1.
How do I ensure the ordering of my Thread Groups?
Also, I need to implement the following scenarios:
Run a single request multiple time by a single user (Single user should create 1000 accounts from a single HTTP request).
Run a multiple requests multiple times by multiple users simultaneously (Multiple users should create 1000 accounts simultaneously from a single HTTP request).
How to do so?
PS: Please read and understand the query carefully before replying.
Concerning consecutive execution of thread groups in test plan: simple check Run Test Group consecutively check-box on the Test Plan configuration screen:
Use e.g. Loop Controller for this:
Thread Group
Number of Threads = 1
Loop Count = 1
...
Loop Controller
Loop Count = N
HTTP Request
...
or even schema without Loop Controller but not so flexible:
Thread Group
Number of Threads = 1
Loop Count = N
...
HTTP Request
...
Use Number of Threads property of standard Thread Group for this together with Ramp-Up Period property:
Thread Group
Number of Threads = N
Ramp-Up Period = 0
Loop Count = 1
...
HTTP Request
...
This will start N simultaneous threads executing same scenario.
Check the Run Thread Groups consecutively (i.e. run groups one at a time) in the Test Plan.
Refer this link. This asks you to check the check box in the main Test Plan
Run Thread Groups consecutively (i.e. one at a time)
http://www.mahsumakbas.net/run-jmeter-thread-groups-consecutively/
Just add more thread groups in your test plan.
In test plan properties -> tick Run Test Group consecutively for step by step execution of thread groups.
Here is the simple solution which I found for Running multiple Thread Groups in particular order:
Check the option "Run Thread Groups consecutively" under "Test Plan"
Order your "Thread Group/s" in the order you want to be executed using drag and drop approach
Regarding Alies Belik answer, there is another way than running thread group consecutively
which is to use Setup Thread Group for the first part.
Regarding setting ramp-up period, it is better to set a value > 0,
which is more realistic one as depending on the number of threads
to start it could delay there startup, the more you have the more it takes time to start.