nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Question on .properties file ident value

lhdavis

TS 6.1 SP1, TST 6

We have made copies of the solutions workflows and their related cfg and properties files, edited them as needed, and have been using them and experienced no issues prior to upgrading to 6.1 SP1.

After our upgrade to TS6.1 SP1, we are seeing strange behavior once we hit the workflow instantiation screen and are using our customized copies of the solutions workflows.

After several debugging techniques to narrow the issue down, I may have found the culprit but wanted to pose the question to the group (as I didn't find any info in the FM). At the start of the solutions workflow .properties file, there is an ident statement such as:
#ident "IWID:src/wft/solutions/configurable_default_submit.properties:f47d0530352fbcb763b782c5da347ddd:..............................."

Has someone broken down what each section of this ident value is for? Specifically I'm looking at the character set after the file name and before the group of periods. What is it's purpose? I believe this is referenced when loaded by the TeamSite:JavaResouceBundle but have yet to decipher it's meaning. Is it meant to simply be a unique identifier among properties files?

Any and all help is much appreciated.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Find more posts tagged with

Comments

Migrateduser

What kind of strange behavior are you seeing?

Michelle Neuringer
Interwoven Engineer

Migrateduser

The ident is used for tracking purposes by our build system. It should have no effect on your system and can be ignored. It is simply a comment.

Brinko Kobrin
Interwoven Staff Engineer

lhdavis

Sorry I've been at a conference earlier in the week. Basically the "strange behavior" that we are seeing is that whenever we submit three or more files to our slightly customized versions of the solutions workflows, our users are met with the following error message in the workflow instantiation screen:

"utf8 version 2 required--this is only version 1.02 at (eval 62) line 3, <FH> line 2.
BEGIN failed--compilation aborted at (eval 62) line 3, <FH> line 2.
(invalid subscript: 2)"

Sometimes it says version 3 is required and gives a slightly different line number.

One or two files submitted within our workflows work fine and it is across the board on our workflows and all users (even Master roles), so we have a low tech workaround. However rarely do our users submit one or two changes at a time which makes this a highly visible issue.

If anyon has seen this I'd love to hear some ideas on how to correct or to narrow down the cause.

I do have a support case open and was just checking on some differences between our customized solutions workflows and the OOTB ones.

Brinko, thanks for the info on the ident tag.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

lhdavis

Upon further review here is the root cause of my problem.

Prior to my 6.1 SP1 upgrade, the following code worked in 6.0 (yes it may not be the most efficient and there are spelling errors but I inheritated it).

<---Start original code --->
# Take the list of files in 'iw_file' and sort them in unencoded form.
my @submit_file = (__ELEM__('iw_file') ? sort __VALUE__('iw_file') : ());

my $include_metadata_task = 0;
my $metadata_extentions = 'html|htm|asp|cfm|doc|dot|xls|ppt|pps|mpp|pub|vsd|pdf|rtf|txt' ;

for (my $i=0; $i < __ELEM__('iw_file'); ++$i)
{

my $file_name = __VALUE__("iw_file[$i]");
my $tempvar = $file_name;
$file_name =~ /\.([^\.]+)$/;
my $extention = $1;
$include_metadata_task = 1
if ( $extention =~ /$metadata_extentions/ );
<---End original code --->

Now in 6.1 SP1, it provides the error mentioned previously.

I have a workaround that does the following, basically replacing all instances of iw_file with my submit_file array and values:

<---Start workaround code --->
my $include_metadata_task = 0;
my $metadata_extentions = 'html|htm|asp|cfm|doc|dot|xls|ppt|pps|mpp|pub|vsd|pdf|rtf|txt' ;

for (my $i=0; $i < @submit_file; ++$i)
{
my $file_name = $submit_file[$i];
my $tempvar = $file_name;
$file_name =~ /\.([^\.]+)$/;
my $extention = $1;
$include_metadata_task = 1
if ( $extention =~ /$metadata_extentions/ );
<---End workaround code --->

My question is why did my original code stop working in 6.1 SP1. What am I missing?

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov