Maybe I'm not explaining it right. If I manually select all the rows and
set them to Approve then hit Submit it works on both mid tier and WUT.
This is default OOB workflow.
If I have another button that sets the fields to all be Approve then I
hit the Submit button, it will not work. If I set a filter to notify of
the TR value of the field, it says it's empty. So it's like the mid tier
doesn't know the field is set even though it displays it on the screen.
The only difference is setting the fields with workflow and manually
selecting the fields.
Dylan
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W
Sent: Monday, May 14, 2007 2:05 PM
To: [email protected]
Subject: Re: Set field on editable table field works in WUT, no
workie on Mid Tier
**
I thought you always had to do your own push to the base form of
the table when using an editable column.
From the 6.3 Basic Guide page 249
For columns in a table field, the options are:
- Editable-Users can change the value in cells in a
column. Editing cells in a table does not affect data in the supporting
form.
On refresh or sort, changes the user makes are lost,
and data displayed in the table will be the data from the parent form.
Also, editing a table does not affect the modify flag
of the form, nor does it affect row colors.
- Read Only-Users cannot change the field value.
- Read Only-HTML-Users cannot change the field value.
In web clients, data in the cell is displayed as HTML.
For example, if a cell contains <b>my cell</b>, it will be displayed as
my cell,
but in Remedy User, it will be displayed as <b>my
cell</b>.
So what I have done in the past is on the Submit button I would
walk the table again and push the changes to the sub form.
Fred
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
Sent: Monday, May 14, 2007 3:53 PM
To: [email protected]
Subject: Re: Set field on editable table field works in WUT, no
workie on Mid Tier
**
Sounds like you are not doing a refresh table action after the
completion of the transaction..
Joe
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Wheeler, Dylan
Sent: Monday, May 14, 2007 4:16 PM
To: [email protected]
Subject: Re: Set field on editable table field works in
WUT, no workie on Mid Tier
**
I'm not doing a push. I'm just doing a set field on the
editable column.
The reasoning is if the approver has 20 approvals, they
hit the button, it sets all the rows to Approve and they can select the
1 or 2 rows that are Reject manually and then submit the approvals.
All the fields get set, I can see it set them all to
Approve, but when you hit the Submit button it acts like the fields are
empty.
I think what your thinking about is if it fires out
order because of phasing and only uses the last row. In this case
though, I see all the rows have been set, so I know it's not firing out
of order.
-----Original Message-----
From: Action Request System discussion
list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms,
Frederick W
Sent: Monday, May 14, 2007 1:09 PM
To: [email protected]
Subject: Re: Set field on editable table field
works in WUT, no workie on Mid Tier
**
When you walk the table, are you referencing the
table column in the push or do you move the table data into temporary
display only fields and use them in the push?
I have seen postings on the list where using a
table column directly can cause problems. I believe it is recommended
to do a set fields and pull the data from the table (during the row
walk) into display only fields and use them in the rest of your
workflow.
Fred
________________________________
From: Action Request System discussion
list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wheeler, Dylan
Sent: Monday, May 14, 2007 3:02 PM
To: [email protected]
Subject: Re: Set field on editable table field
works in WUT, no workie on Mid Tier
Hi Listers,
I sent this last Friday late in the day. Nobody
responded so I hope it was because everyone was off work and out
enjoying the beginning of their weekend :)
I still can't figure out what's going wrong with
it though so any help would be greatly appreciated.
------------------------------------------------------------------------
----------------------
I'm having a problem and I can't figure
out what's going wrong.
On ARS 6.3, I added a button on the
approval central console. The button walks the table and sets all the
approvals to Approve. They can then just hit the submit button to
approve all. It works fine in the WUT.
On the Mid Tier it will set the fields
but when they hit Submit it doesn't do anything. It looks like the Mid
Tier is not seeing the set field even though it's displaying on the
screen. Anyone run into anything like this?
-------------
Dylan Wheeler
Production Control Analyst Principal
IT Operations
Downey Savings & Loan Association, F.A.
Email: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
__20060125_______________________This posting was submitted with
HTML in it___
This message and any attachments are for the intended recipient(s) only and may
contain privileged, confidential and/or proprietary information about Downey
Savings or its customers, which Downey Savings does not intend to disclose to
the public. If you received this message by mistake, please notify the sender
by reply e-mail and delete the message and attachments.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
