Cancel Process

Jhstephenson

Is there some trick to Cancelling an Active Process?

For example:
I have a process that updates a certain attribute in a BO.
I start the process and have it run in background after 5 seconds (Which is another topic in itself, because I don't know whose clock that 5 seconds runs on but it is more like about 1 minute before a process falls into the background).
I run a query on the BO, while the process is running, to see if it looks like what I want. It isn't.
So, I want to cancel the Process.
I bring up the Active Processes screen and hit the cancel button 975 times on the Process I want to cancel (That may be a slight exaggeration).
Nothing happens.
The only way I can end the process is to shut down the Aware Server and then restart it.
Which then results in a process staying in the Active Processes list with a 'Waiting' status forever.

Am I missing something in the way processes can/should be cancelled?

Jaymer

great question.
I look forward to this answer.

tford

Following.

Rennur

In my opinion, this issue is subject to each individual application.

Things to check:
1) Incorrect/faulty design/use of Business object groups.
2) Ensure all SHOW SECTION_START, SECTION_END in document templates are properly enclosed.
3) Make sure Process refresh feature in BO forms is utilised.
4) Users may have logged in to the app multiple times using browser tabs. This can cause unexpected problems.
5) Process workflow and branching consistencies.

https://github.com/RennurApps/AwareIM-resources/issues/1

Cheers

tford

I start the process and have it run in background after 5 seconds (Which is another topic in itself, because I don't know whose clock that 5 seconds runs on but it is more like about 1 minute before a process falls into the background).

I bring up the Active Processes screen and hit the cancel button 975 times on the Process I want to cancel (That may be a slight exaggeration).
Nothing happens.

Renur,

re: 5) Process workflow and branching consistencies.

Can you give an example of how #5 would impact with of the above quoted issues from Jhstephenson?

Thanks!

Jhstephenson

Rennur wrote
In my opinion, this issue is subject to each individual application.

Rennur, see below...

Things to check:
1) Incorrect/faulty design/use of Business object groups.

No Business Object groups defined

2) Ensure all SHOW SECTION_START, SECTION_END in document templates are properly enclosed.

This doesn't involve a document.

3) Make sure Process refresh feature in BO forms is utilised.

This really doesn't involve a form.

4) Users may have logged in to the app multiple times using browser tabs. This can cause unexpected problems.

This is in Test mode. No other users logged in.

5) Process workflow and branching consistencies.

I am not quite sure what this would have to do with it.

https://github.com/RennurApps/AwareIM-resources/issues/1

Cheers

Rennur

5) Process workflow and branching consistencies.

Process workflow and structure (hierarchy) of combining multiple processes. Branching is probably the wrong term used.

E.g.
Process 1 (Core)

FIND BO1 WHERE [insert criteria] IN BATCHES OF 1
Process 2

Process 2
FIND BO2 IN BATCHES OF 1

CREATE BO3 WITH BO3.BO1=BO1, BO3.BO2=BO2
(run) Process 3

Process 1 (Core)

EDIT BO1 USING 'EDIT FORM'
DISPLAY MESSAGE 'Some text'
VIEW BO1 USING 'EDIT FORM'

Jhstephenson

In this particular case the process does the following:

FIND CaseNotes WHERE CaseNotes.Note='requested discovery' AND CaseNotes.NoteType IS UNDEFINED IN BATCHES OF 1
FIND mfNoteTypes WHERE mfNoteTypes.NoteType='REQUEST FOR DISCOVERY'
INSERT mfNoteTypes IN CaseNotes.NoteType

Pretty basic stuff really: Find all the records that match a couple of criteria, find the master file record that matches the type of request I am looking for, and then update the attribute in the BO.

It isn't rocket science.

But, the issue really is that it doesn't seem to matter how complex or simple the process is, once started it can be almost impossible to cancel it.

Jaymer

2 things
1) You don't need to do the 2nd FIND EVERY LOOP CYCLE - its not changing. Perform this FIND once.
2) Assuming you don't change per #1, in order for this to work YOU MIGHT need to call a subprocess after the 1st find.

proc1: find casenotes batches of 1
call proc2

proc2: find mfnote...
insert

Jhstephenson

Jaymer,

That would certainly make the process more efficient.

But, is that really going to impact the ability to Cancel a running process?

Jim