Hi all,
help me in understanding the Syntax of the below Run Process Command.
@@:Application-Delete-Entry FormName $Request ID$
what does @@: Stands for? Need more details on this.

Regards,
Viji

Hi,

First, this syntax is used only in active links.

@@: means to run the process on the current server.
@servername: means to run the process on servername server.

Small easy way : In the documentation, all processes in uppercase are executed on client side and all processes with a mix of uppercase and lowercase are executed on server side.

Hi,
Related to this question:

- how can more than one selected entries being deleted on a form (not on a table field related to a form)?, i.e., how can I loop through the selected entries just the same way an Admin would do using "Actions -> Delete" user option.

- if a active link guide is needed, could you please provide me a step by step procedure to achieving this? Should this guide be executed from another form?

Thanks,
Björn.

I do not know a way to delete the selected entrys in the resultlist of an form without using Actions->Delete.

The deletion of multiple entrys could be achieved with Application-Query-Delete-Entry <form> <qualification_string> or with an table loop using Application-Delete-Entry <form> <Request-ID>. Which is to use depends on needs.

Hi,
I'm trying to use Application-Delete-Entry but I'm not able to loop with an Active Link Guide, which is needed to loop a table, isn´t it?

And also, if using Application-Query-Delete-Entry, how can I specify as qualification string "the selected, i.e., the highlighted entries"?

TIA,
Björn.

Use the keyword ROWSELECTED in your Run-If... make sure to have your Request ID as one of the columns, so that you know which record to delete.

As far as the Active Link Guide... refer to the Workflow section of the Remedy Administrator Guides.

Good luck,

Why are you not able to loop over the table?

Create a guide with one al which makes the deletion (Application-Delete-Entry) and create another al which calls this guide. At this point (Call Guide) choose the table field to loop over and choose the option "Table Loop Selected Rows Only".

Another option is to use Application-Query-Delete-Entry. In this case you create an al within an guide which builds the qualification (e.g. request-id of the current entry in the table field). This guide is called by another al as described before. After the call guide use Application-Query-Delete-Entry with the qualifier bild i the guide.

I suggest to use the first version.

Hi,
Perhaps I'm missing something. I'm trying all you explained with no result.

I'll try to explain better the problem:

- I've two forms (FormA, FormB)
- On FormA I've:

1. A Table Field showing some FormB columns (Request ID and other fields)

2. A button that should delete the selected/highlighted (isn´t it the same thing???) TF entries, i.e. that should delete the selected entries on FormB.

For achieving this I've developed the following:

1. An AL that runs on FormB, with a RunProcess action:
@@:Application-Delete-Entry <schema> <id>

2. An AL Guide including the aforementioned AL

3. An AL that runs on FormA, on button click (with Table loop on selected records and all this things...)

NO RESULTS. After clicking on FormA button, FormB opens in submit mode and nothing seems to happen.

I think the ARS documentation is a little bit poor:
-Where should I define the ROWSELECTED keyword?
-Is it important? If I check the table loop (over FormA TF)and the loop only on selected rows, isn't this enough?
-I don´t know how to define the RunProcess parameters; the $SCHEMA$ keyword will work or will I have to pass the name of the form? The second parameter, the request-id, how should I define this?

I'm using a test VM environment with ARS63p15

TIA
Björn.

Hi,

Using table loop on selected records, you don't need to specify $ROWSELECTED$...

As you run this process on FormA, you must not use $SCHEMA$ keyword to run this process...

You should use :
@@:Application-Delete-Entry "FormB" $col_FormB_ReqyestID

Hi,
Finally I got it. I was selecting the wrong form for executing the AL with the RunProcess "delete" action.

Many thanks to you ALL for your kind help.

Björn.