Re: Walking table, reading and setting hi-liting rows SOLVED
Since it is not possible to select multiple table rows via workflow I submitted that as an enhancement request. Then I basically followed Frederick's suggestion (see below). Two things I learned: 1 In order to set workflow based on double-clicking a table row you have to go to Display tab and un-check Table Drill Down. 2 On display, I needed to re-select the table rows based on the storage field, but I found that the table rows were getting set before the table was displayed, and then the display blew away the settings. So I un-checked Refresh on Entry Change, then on Display, did a Change Fields refresh, then set the rows. Thanks again, Frederick, and all others who responded. Dwayne Martin James Madison University From: Grooms, Frederick W [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows In-Reply-To: A[EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Like I said I could not highlite multiple rows thru workflow. My solution was to do the following: Add a Display Only field on the form (I used a 3 character field) Add this Display Only field as a column in the table (Yes you can add Display only fields from the form that holds the table as columns in the table). I called my column Selected In your Display workflow do the following Refresh the table walk the table while walking the table if 'your storage field' like % + 'Entry ID col' + % then set the display only field to Yes and set the column to Yes else clear the display only field I also changed it so that users double click on a row instead of multiple selecting and that set's the Selected column to Yes for that row (If Col = Yes clear the col and the Display Only else set both. Fred ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Walking table, reading and setting hi-liting rows
Thad,
Thanks for the idea. I'll give it a try.
Dwayne
Original message
Date: Wed, 18 Jun 2008 15:16:58 -0700
From: Thad K Esser [EMAIL PROTECTED]
Subject: Re: Walking table, reading and setting hi-liting rows
To: arslist@ARSLIST.ORG
**
Dwayne,
Your original post said you are on version 7.1. I
haven't played with it much, but page 368 of the
Form and Application Objects manual says you can
change the colors of rows in tables based on
selection fields. If you combined that with Fred's
suggestion below, you could set the foreground color
to white and the background color to black when the
status was Yes. It wouldn't truly be a selected
row, but it would look that way to the user. I
don't know how well that would play out in practice
for what you are doing, but its crazy enough that it
just might work.
Thad Esser
Remedy Developer
Argue for your limitations, and sure enough,
they're yours.-- Richard Bach
Grooms, Frederick WTo arslist@ARSLIST.ORG
[EMAIL PROTECTED] cc
Sent by: Action RequestSubject Re: Walking table,
System discussion reading and setting
list(ARSList) hi-liting rows
arslist@ARSLIST.ORG
06/18/2008 02:47 PM
+-+
| Please respond to |
| arslist@ARSLIST.ORG |
+-+
Like I said I could not highlite multiple rows thru
workflow.
My solution was to do the following:
Add a Display Only field on the form (I used a 3
character field)
Add this Display Only field as a column in the table
(Yes you can add
Display only fields from the form that holds the
table as columns in the
table). I called my column Selected
In your Display workflow do the following
Refresh the table
walk the table
while walking the table
if 'your storage field' like % + 'Entry ID
col' + %
then set the display only field to Yes and
set the column to
Yes
else clear the display only field
I also changed it so that users double click on a
row instead of
multiple selecting and that set's the Selected
column to Yes for that
row (If Col = Yes clear the col and the Display
Only else set both.
Fred
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Dwayne
Martin
Sent: Wednesday, June 18, 2008 2:45 PM
To: arslist@ARSLIST.ORG
Subject: Re: Walking table, reading and setting
hi-liting rows
Thank you, Frederick, Andrew and Frank, for your
replies. I got waylaid
and hope we haven't lost our train of thot.
What I am trying to do is:
1. Let the user hi-lite some rows in a table. When
the entry is saved,
write a list of hi-lited rows into a field, which is
saved with the
record.
2. When the record is displayed, read the field and
use the value in the
field to hi-lite the same rows that were selected in
the previous
session.
The first step turned out to ridiculously simple.
All I had to do is
have an Active Link call a guide that does a table
loop and Table Loop
Selected Rows Only, and it creates a neat little
list of hi-lited rows.
I think Step 2 is impossible. As Frederick has
pointed out you [can]
not set the highlite on multiple rows thru
workflow, The Workflow
Objects 7.1 manual, p223 shows how to select a row
by setting the value
of the table field to the desired row number. But
it says nothing about
selecting multiple rows (ie simulating a
cntrl-click).
It also appears that you can't even read a table on
Display. My storage
field keeps a list based on an Entry ID col field
in the table. I set
up an Active Link to set the table to 0 on Display
(un-hilite the first
row), then call a guide that walks the table, and if
the field where I
was storing the values is LIKE % + $Entry ID col$
+ %, display a
message with the value in the Entry ID col. The
message displayed for
every row, whether the values matched or not, but
the Entry ID col
value was null. The table didn't fill till the
messages stopped
displaying, and when it did, the first row was
hi-lited. It appears
that the Display Active Links fire before the
tables are filled, so
you really can't get any info from a table when a
record is displayed.
I am used to telling my customers that Remedy can
do anything! But it
looks like I have hit a dead end this time. Could
someone please prove
me wrong.
Dwayne Martin
Original message
Date: Mon, 16 Jun 2008 09:28:47 -0500
From: Grooms, Frederick W
[EMAIL
Re: Walking table, reading and setting hi-liting rows
I think you will find that the color is only set for the rows when the table is refreshed. Changing the selection value after refresh does not change the row color. (At least in v6.3 it did not work that way. Maybe 7.1 will be different, but I doubt it.) And frankly, given any ADA requirements, using color is a bad way to communicate with users. I personally prefer the extra column approach. You can even combine the two if you want to as well. The extra column could be 'Display Type' = Read Only-HTML and stuff HTML into each cell to color the page and add text to match the state for the row. So the background could be green and you could put the word green in the cell too. ( Just a thought) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Wed, Jun 18, 2008 at 6:16 PM, Thad K Esser [EMAIL PROTECTED] wrote: ** Dwayne, Your original post said you are on version 7.1. I haven't played with it much, but page 368 of the Form and Application Objects manual says you can change the colors of rows in tables based on selection fields. If you combined that with Fred's suggestion below, you could set the foreground color to white and the background color to black when the status was Yes. It wouldn't truly be a selected row, but it would look that way to the user. I don't know how well that would play out in practice for what you are doing, but its crazy enough that it just might work. Thad Esser Remedy Developer Argue for your limitations, and sure enough, they're yours.-- Richard Bach ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Walking table, reading and setting hi-liting rows
Thanks, Carey, I did a search in the Form and Application and Workflow Objects manuals for extra column but didn't find anything. Where can I get more info? Dwayne Original message Date: Thu, 19 Jun 2008 10:03:22 -0400 From: Carey Matthew Black [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows To: arslist@ARSLIST.ORG I think you will find that the color is only set for the rows when the table is refreshed. Changing the selection value after refresh does not change the row color. (At least in v6.3 it did not work that way. Maybe 7.1 will be different, but I doubt it.) And frankly, given any ADA requirements, using color is a bad way to communicate with users. I personally prefer the extra column approach. You can even combine the two if you want to as well. The extra column could be 'Display Type' = Read Only-HTML and stuff HTML into each cell to color the page and add text to match the state for the row. So the background could be green and you could put the word green in the cell too. ( Just a thought) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Wed, Jun 18, 2008 at 6:16 PM, Thad K Esser [EMAIL PROTECTED] wrote: ** Dwayne, Your original post said you are on version 7.1. I haven't played with it much, but page 368 of the Form and Application Objects manual says you can change the colors of rows in tables based on selection fields. If you combined that with Fred's suggestion below, you could set the foreground color to white and the background color to black when the status was Yes. It wouldn't truly be a selected row, but it would look that way to the user. I don't know how well that would play out in practice for what you are doing, but its crazy enough that it just might work. Thad Esser Remedy Developer Argue for your limitations, and sure enough, they're yours.-- Richard Bach ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Walking table, reading and setting hi-liting rows
Excuse me, Carey. I misunderstood what you were saying. You were referring to Frederick’s solution below. That look’s do-able, and I’ll give it a try. Thank you, Carey, and Fred, and all others who responded. Dwayne Date: Thu, 19 Jun 2008 10:03:22 -0400 Reply-To: arslist@ARSLIST.ORG Sender: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG From: Carey Matthew Black [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows In-Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline I think you will find that the color is only set for the rows when the table is refreshed. Changing the selection value after refresh does not change the row color. (At least in v6.3 it did not work that way. Maybe 7.1 will be different, but I doubt it.) And frankly, given any ADA requirements, using color is a bad way to communicate with users. I personally prefer the extra column approach. You can even combine the two if you want to as well. The extra column could be 'Display Type' = Read Only-HTML and stuff HTML into each cell to color the page and add text to match the state for the row. So the background could be green and you could put the word green in the cell too. ( Just a thought) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. ** Date: Wed, 18 Jun 2008 16:47:29 -0500 Reply-To: arslist@ARSLIST.ORG Sender: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG From: Grooms, Frederick W [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows In-Reply-To: A[EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Like I said I could not highlite multiple rows thru workflow. My solution was to do the following: Add a Display Only field on the form (I used a 3 character field) Add this Display Only field as a column in the table (Yes you can add Display only fields from the form that holds the table as columns in the table). I called my column Selected In your Display workflow do the following Refresh the table walk the table while walking the table if 'your storage field' like % + 'Entry ID col' + % then set the display only field to Yes and set the column to Yes else clear the display only field I also changed it so that users double click on a row instead of multiple selecting and that set's the Selected column to Yes for that row (If Col = Yes clear the col and the Display Only else set both. Fred
Re: Walking table, reading and setting hi-liting rows
Thank you, Frederick, Andrew and Frank, for your replies. I got waylaid and hope we haven’t lost our train of thot. What I am trying to do is: 1. Let the user hi-lite some rows in a table. When the entry is saved, write a list of hi-lited rows into a field, which is saved with the record. 2. When the record is displayed, read the field and use the value in the field to hi-lite the same rows that were selected in the previous session. The first step turned out to ridiculously simple. All I had to do is have an Active Link call a guide that does a table loop and “Table Loop Selected Rows Only,” and it creates a neat little list of hi-lited rows. I think Step 2 is impossible. As Frederick has pointed out “you [can] not set the highlite on multiple rows thru workflow,” The “Workflow Objects” 7.1 manual, p223 shows how to select a row by setting the value of the table field to the desired row number. But it says nothing about selecting multiple rows (ie simulating a cntrl-click). It also appears that you can’t even read a table on Display. My storage field keeps a list based on an “Entry ID col” field in the table. I set up an Active Link to set the table to 0 on Display (un-hilite the first row), then call a guide that walks the table, and if the field where I was storing the values is “LIKE “%” + $Entry ID col$ + “%”, display a message with the value in the “Entry ID col”. The message displayed for every row, whether the values matched or not, but the “Entry ID col” value was null. The table didn’t fill till the messages stopped displaying, and when it did, the first row was hi-lited. It appears that the “Display” Active Links fire before the tables are filled, so you really can’t get any info from a table when a record is displayed. I am used to telling my customers that “Remedy can do anything!” But it looks like I have hit a dead end this time. Could someone please prove me wrong. Dwayne Martin Original message Date: Mon, 16 Jun 2008 09:28:47 -0500 From: Grooms, Frederick W [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows To: arslist@ARSLIST.ORG ** In 6.3 I tried to do just what Dwayne is wanting and found you could not set the highlite on multiple rows thru workflow. I had to settle with making a Selected column and displaying that when re-displaying the list to the user. Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Friday, June 13, 2008 2:35 PM To: arslist@ARSLIST.ORG Subject: Re: Walking table, reading and setting hi-liting rows ** I do not have the 7 docs handy but I know there is lot of information in the 6.3 docs about table walking, specifically about what you are asking. 1. Remedy knows if the row is selected using the $ROWSELECTED$ keyword. I believe it even knows which row was selected as the primary and which was selected as the secondary. 2. In order to highlite a row you need to reference the table name and a row number in a set fields action. Page 659 in 6.3 basic guide has everything you need to know. Look for a Workflow Extras section in the 7 docs. On Fri, Jun 13, 2008 at 2:43 PM, Dwayne Martin [EMAIL PROTECTED] wrote: Dear List, I am sure this is spelled out very plainly in the documentation, but I can't seem to find it. I want the user to be able to hi-lite table rows, save the entry, and have those same table rows hi-lited when the entry is re-displayed. So the user will cntl-click several rows to hi-lite them. Then on save, an Active Link Guide will walk the table, and if the row is hi-lited it will write the Entry ID for the row into a Char field. But how does it know if the row is hi-lited? On Display, another AL Guide will walk the table, and if Char Field is LIKE % + 'Entry ID col' + % it will hi-lite the row. But how does it do that? Actually, I'd be happy if somebody could point out where this is explained in the manual. (ARS 7.1, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___
Re: Walking table, reading and setting hi-liting rows
Like I said I could not highlite multiple rows thru workflow. My solution was to do the following: Add a Display Only field on the form (I used a 3 character field) Add this Display Only field as a column in the table (Yes you can add Display only fields from the form that holds the table as columns in the table). I called my column Selected In your Display workflow do the following Refresh the table walk the table while walking the table if 'your storage field' like % + 'Entry ID col' + % then set the display only field to Yes and set the column to Yes else clear the display only field I also changed it so that users double click on a row instead of multiple selecting and that set's the Selected column to Yes for that row (If Col = Yes clear the col and the Display Only else set both. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin Sent: Wednesday, June 18, 2008 2:45 PM To: arslist@ARSLIST.ORG Subject: Re: Walking table, reading and setting hi-liting rows Thank you, Frederick, Andrew and Frank, for your replies. I got waylaid and hope we haven't lost our train of thot. What I am trying to do is: 1. Let the user hi-lite some rows in a table. When the entry is saved, write a list of hi-lited rows into a field, which is saved with the record. 2. When the record is displayed, read the field and use the value in the field to hi-lite the same rows that were selected in the previous session. The first step turned out to ridiculously simple. All I had to do is have an Active Link call a guide that does a table loop and Table Loop Selected Rows Only, and it creates a neat little list of hi-lited rows. I think Step 2 is impossible. As Frederick has pointed out you [can] not set the highlite on multiple rows thru workflow, The Workflow Objects 7.1 manual, p223 shows how to select a row by setting the value of the table field to the desired row number. But it says nothing about selecting multiple rows (ie simulating a cntrl-click). It also appears that you can't even read a table on Display. My storage field keeps a list based on an Entry ID col field in the table. I set up an Active Link to set the table to 0 on Display (un-hilite the first row), then call a guide that walks the table, and if the field where I was storing the values is LIKE % + $Entry ID col$ + %, display a message with the value in the Entry ID col. The message displayed for every row, whether the values matched or not, but the Entry ID col value was null. The table didn't fill till the messages stopped displaying, and when it did, the first row was hi-lited. It appears that the Display Active Links fire before the tables are filled, so you really can't get any info from a table when a record is displayed. I am used to telling my customers that Remedy can do anything! But it looks like I have hit a dead end this time. Could someone please prove me wrong. Dwayne Martin Original message Date: Mon, 16 Jun 2008 09:28:47 -0500 From: Grooms, Frederick W [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows To: arslist@ARSLIST.ORG ** In 6.3 I tried to do just what Dwayne is wanting and found you could not set the highlite on multiple rows thru workflow. I had to settle with making a Selected column and displaying that when re-displaying the list to the user. Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Friday, June 13, 2008 2:35 PM To: arslist@ARSLIST.ORG Subject: Re: Walking table, reading and setting hi-liting rows ** I do not have the 7 docs handy but I know there is lot of information in the 6.3 docs about table walking, specifically about what you are asking. 1. Remedy knows if the row is selected using the $ROWSELECTED$ keyword. I believe it even knows which row was selected as the primary and which was selected as the secondary. 2. In order to highlite a row you need to reference the table name and a row number in a set fields action. Page 659 in 6.3 basic guide has everything you need to know. Look for a Workflow Extras section in the 7 docs. On Fri, Jun 13, 2008 at 2:43 PM, Dwayne Martin [EMAIL PROTECTED] wrote: Dear List, I am sure this is spelled out very plainly in the documentation, but I can't seem to find it. I want the user to be able to hi-lite table rows, save the entry, and have those same table rows hi-lited when the entry is re-displayed. So the user will cntl-click several rows to hi-lite them. Then on save, an Active Link Guide will walk the table, and if the row is hi-lited it will write the Entry ID for the row into a Char field
Re: Walking table, reading and setting hi-liting rows
Dwayne, Your original post said you are on version 7.1. I haven't played with it much, but page 368 of the Form and Application Objects manual says you can change the colors of rows in tables based on selection fields. If you combined that with Fred's suggestion below, you could set the foreground color to white and the background color to black when the status was Yes. It wouldn't truly be a selected row, but it would look that way to the user. I don't know how well that would play out in practice for what you are doing, but its crazy enough that it just might work. Thad Esser Remedy Developer Argue for your limitations, and sure enough, they're yours.-- Richard Bach Grooms, Frederick W [EMAIL PROTECTED] Sent by: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG 06/18/2008 02:47 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: Walking table, reading and setting hi-liting rows Like I said I could not highlite multiple rows thru workflow. My solution was to do the following: Add a Display Only field on the form (I used a 3 character field) Add this Display Only field as a column in the table (Yes you can add Display only fields from the form that holds the table as columns in the table). I called my column Selected In your Display workflow do the following Refresh the table walk the table while walking the table if 'your storage field' like % + 'Entry ID col' + % then set the display only field to Yes and set the column to Yes else clear the display only field I also changed it so that users double click on a row instead of multiple selecting and that set's the Selected column to Yes for that row (If Col = Yes clear the col and the Display Only else set both. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin Sent: Wednesday, June 18, 2008 2:45 PM To: arslist@ARSLIST.ORG Subject: Re: Walking table, reading and setting hi-liting rows Thank you, Frederick, Andrew and Frank, for your replies. I got waylaid and hope we haven't lost our train of thot. What I am trying to do is: 1. Let the user hi-lite some rows in a table. When the entry is saved, write a list of hi-lited rows into a field, which is saved with the record. 2. When the record is displayed, read the field and use the value in the field to hi-lite the same rows that were selected in the previous session. The first step turned out to ridiculously simple. All I had to do is have an Active Link call a guide that does a table loop and Table Loop Selected Rows Only, and it creates a neat little list of hi-lited rows. I think Step 2 is impossible. As Frederick has pointed out you [can] not set the highlite on multiple rows thru workflow, The Workflow Objects 7.1 manual, p223 shows how to select a row by setting the value of the table field to the desired row number. But it says nothing about selecting multiple rows (ie simulating a cntrl-click). It also appears that you can't even read a table on Display. My storage field keeps a list based on an Entry ID col field in the table. I set up an Active Link to set the table to 0 on Display (un-hilite the first row), then call a guide that walks the table, and if the field where I was storing the values is LIKE % + $Entry ID col$ + %, display a message with the value in the Entry ID col. The message displayed for every row, whether the values matched or not, but the Entry ID col value was null. The table didn't fill till the messages stopped displaying, and when it did, the first row was hi-lited. It appears that the Display Active Links fire before the tables are filled, so you really can't get any info from a table when a record is displayed. I am used to telling my customers that Remedy can do anything! But it looks like I have hit a dead end this time. Could someone please prove me wrong. Dwayne Martin Original message Date: Mon, 16 Jun 2008 09:28:47 -0500 From: Grooms, Frederick W [EMAIL PROTECTED] Subject: Re: Walking table, reading and setting hi-liting rows To: arslist@ARSLIST.ORG ** In 6.3 I tried to do just what Dwayne is wanting and found you could not set the highlite on multiple rows thru workflow. I had to settle with making a Selected column and displaying that when re-displaying the list to the user. Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Friday, June 13, 2008 2:35 PM To: arslist@ARSLIST.ORG Subject: Re: Walking table, reading and setting hi-liting rows ** I do not have the 7 docs handy but I know there is lot of information in the 6.3 docs about table walking, specifically about what you are asking. 1. Remedy knows if the row is selected using the $ROWSELECTED
Re: Walking table, reading and setting hi-liting rows
In 6.3 I tried to do just what Dwayne is wanting and found you could not set the highlite on multiple rows thru workflow. I had to settle with making a Selected column and displaying that when re-displaying the list to the user. Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Friday, June 13, 2008 2:35 PM To: arslist@ARSLIST.ORG Subject: Re: Walking table, reading and setting hi-liting rows ** I do not have the 7 docs handy but I know there is lot of information in the 6.3 docs about table walking, specifically about what you are asking. 1. Remedy knows if the row is selected using the $ROWSELECTED$ keyword. I believe it even knows which row was selected as the primary and which was selected as the secondary. 2. In order to highlite a row you need to reference the table name and a row number in a set fields action. Page 659 in 6.3 basic guide has everything you need to know. Look for a Workflow Extras section in the 7 docs. On Fri, Jun 13, 2008 at 2:43 PM, Dwayne Martin [EMAIL PROTECTED] wrote: Dear List, I am sure this is spelled out very plainly in the documentation, but I can't seem to find it. I want the user to be able to hi-lite table rows, save the entry, and have those same table rows hi-lited when the entry is re-displayed. So the user will cntl-click several rows to hi-lite them. Then on save, an Active Link Guide will walk the table, and if the row is hi-lited it will write the Entry ID for the row into a Char field. But how does it know if the row is hi-lited? On Display, another AL Guide will walk the table, and if Char Field is LIKE % + 'Entry ID col' + % it will hi-lite the row. But how does it do that? Actually, I'd be happy if somebody could point out where this is explained in the manual. (ARS 7.1, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University __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
Walking table, reading and setting hi-liting rows
Dear List, I am sure this is spelled out very plainly in the documentation, but I can’t seem to find it. I want the user to be able to hi-lite table rows, save the entry, and have those same table rows hi-lited when the entry is re-displayed. So the user will cntl-click several rows to hi-lite them. Then on save, an Active Link Guide will walk the table, and if the row is hi-lited it will write the Entry ID for the row into a Char field. But how does it know if the row is hi-lited? On Display, another AL Guide will walk the table, and if Char Field is LIKE “%” + ‘Entry ID col’ + “%” it will hi-lite the row. But how does it do that? Actually, I’d be happy if somebody could point out where this is explained in the manual. (ARS 7.1, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University
Re: Walking table, reading and setting hi-liting rows
You could use the keyword $ROWSELECTED$ for to check if row is selected. Extract from the manual $ROWSELECTED$ -- Evaluates if row in table field is selected: - 0 = Not selected - 1 = Secondary selection - 2 = Primary selection This keyword is only valid in the context of a table loop guide. On Fri, Jun 13, 2008 at 11:43 AM, Dwayne Martin [EMAIL PROTECTED] wrote: Dear List, I am sure this is spelled out very plainly in the documentation, but I can't seem to find it. I want the user to be able to hi-lite table rows, save the entry, and have those same table rows hi-lited when the entry is re-displayed. So the user will cntl-click several rows to hi-lite them. Then on save, an Active Link Guide will walk the table, and if the row is hi-lited it will write the Entry ID for the row into a Char field. But how does it know if the row is hi-lited? On Display, another AL Guide will walk the table, and if Char Field is LIKE % + 'Entry ID col' + % it will hi-lite the row. But how does it do that? Actually, I'd be happy if somebody could point out where this is explained in the manual. (ARS 7.1, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: Walking table, reading and setting hi-liting rows
I do not have the 7 docs handy but I know there is lot of information in the 6.3 docs about table walking, specifically about what you are asking. 1. Remedy knows if the row is selected using the $ROWSELECTED$ keyword. I believe it even knows which row was selected as the primary and which was selected as the secondary. 2. In order to highlite a row you need to reference the table name and a row number in a set fields action. Page 659 in 6.3 basic guide has everything you need to know. Look for a Workflow Extras section in the 7 docs. On Fri, Jun 13, 2008 at 2:43 PM, Dwayne Martin [EMAIL PROTECTED] wrote: Dear List, I am sure this is spelled out very plainly in the documentation, but I can't seem to find it. I want the user to be able to hi-lite table rows, save the entry, and have those same table rows hi-lited when the entry is re-displayed. So the user will cntl-click several rows to hi-lite them. Then on save, an Active Link Guide will walk the table, and if the row is hi-lited it will write the Entry ID for the row into a Char field. But how does it know if the row is hi-lited? On Display, another AL Guide will walk the table, and if Char Field is LIKE % + 'Entry ID col' + % it will hi-lite the row. But how does it do that? Actually, I'd be happy if somebody could point out where this is explained in the manual. (ARS 7.1, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
