Fred, I think this is a strangeness in how AR logs, actually.

I've got two filters set up on my Linux 7.1 patch 1 VM. They both fire on
modify and I'm testing them on at a time.

 

The first uses Set Fields: $PROCESS$ PERFORM-ACTION-ADD-ATTACHMENT 536880912
"/root/whatar.txt"

 

The second uses Run Process: PERFORM-ACTION-ADD-ATTACHMENT 536880912
"/root/whatar.txt"

 

The filter log from the client side and the server side for each test are
below.

 

First, the Set Fields test, client-side log. Notice the logs stripped out
the $PROCESS$ key word. In fact, I couldn't use the remainder of that line
in a Set Fields as ARAdmin would complain about the math.

 

<WFLG> /* Mon Feb 25 2008 09:48:12 */

<WFLG> Workflow Trace Log -- ON

<WFLG> BMC Remedy User      Version 7.1.00 (patch 001)

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
> /* Mon Feb 25 2008 09:41:45.0352 */     Start filter processing (phase 1)
-- Operation - SET on NCC:SSC:External Process Report - 000000000000001

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
> /* Mon Feb 25 2008 09:41:45.0355 */     Checking "NCC:SCC:External Process
Report_Add Attachment_Set Fields" (500)

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>    --> Passed -- perform actions

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>         0: Set Fields

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>                   PERFORM-ACTION-ADD-ATTACHMENT 536880912
"/root/whatar.txt"

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>                   Exit code: 0  Value: 0

<FLTR> <TID: 0037137312> <RPC ID: 0000002663> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>               Short Description (8) = 0

 

And the file did not get placed into the attachment field.

 

Next, using the Run Process action. Client-side log:

 

<WFLG> /* Mon Feb 25 2008 09:53:06 */

<WFLG> Workflow Trace Log -- ON

<WFLG> BMC Remedy User      Version 7.1.00 (patch 001)

<FLTR> <TID: 0069954464> <RPC ID: 0000002755> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
> /* Mon Feb 25 2008 09:45:21.7513 */     Start filter processing (phase 1)
-- Operation - SET on NCC:SSC:External Process Report - 000000000000001

<FLTR> <TID: 0069954464> <RPC ID: 0000002755> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
> /* Mon Feb 25 2008 09:45:21.7515 */     Checking "NCC:SCC:External Process
Report_Add Attachment_Run Process" (500)

<FLTR> <TID: 0069954464> <RPC ID: 0000002755> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>    --> Passed -- perform actions

<FLTR> <TID: 0069954464> <RPC ID: 0000002755> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>         0: Process

<FLTR> <TID: 0069954464> <RPC ID: 0000002755> <Queue: Fast      >
<Client-RPC: 390620   > <USER: Demo
>               PERFORM-ACTION-ADD-ATTACHMENT 536880912 "/root/whatar.txt"

 

And the attachment is still not there.

 

Also, if I point either filter to a file that does not exist I get: "ARERR
[295] File pointer is NULL or not a valid file pointer in the client."

 

Considering this is a FILTER and I want it to attach a file that lives on
the SERVER, I'm a bit confused by the phraseology in the error (.file
pointer in the _client_)

 

I then exported my form and workflow and imported them onto a windows 7.0.1
Patch 5 VM. I changed the location of the file to "c:\whatar.txt" and tested
both methods.

 

I'm afraid it gets worse and not better.

 

The Run Process filter acts the same exact way. However, the Set Fields
filter, which sets Short Description (and should set it to 0 if the file is
found and attached) is setting it to NULL on Windows which causes: 

 

"ARERR [552] Failure during SQL operation to the database : The statement
has been terminated. Cannot insert the value NULL into column 'C8', table
'ARSystem.dbo.T1576'; column does not allow nulls. UPDATE fails. (SQL Server
515)"

 

Again, I get the 295 error if I point to a non-existent file.

 

I even tried adding a character field to hold the name of the file I want to
attach and that has the same issues. 

J.T. Shyman 
Column Technologies 

  

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Sunday, February 24, 2008 7:04 PM
To: [email protected]
Subject: Re: PERFORM-ACTION-ADD-ATTACHMENT from a filter

 

J.T.,

Re-looking at your logs I noticed you tried a Set Fields action using just
the add attachment command and a Run Process action using $PROCESS$ and the
add attachment command.

 

Remove $PROCESS$ from the Run Process action command line or add it to the
Set Fields action

 

Fred

 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to