Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #1 
We have seen reported that the %Field construct is no longer available.

There seems to be a workaround. There is an object called Current. You can access the Form object from this, when 'in' a Form.

The syntax is this:
Quote:
Current.Fields.<fieldname>.DataValue

It returns an object. If you know what type it is, and you should, you can then cast it appropriately.

This is, of course, part of the full undocumentation.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Nappy

Avatar / Picture

Guru
Registered:
Posts: 1,087
Reply with quote  #2 
The risk is that this may indeed be the way or it's an undocumented non suported way.

If only we had the docs.....

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.

PS that's for V6/7 for V9 the problem is V9 at the moment ;)
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #3 
that idea in itself gives me pause for thought. We will be seeing a large number of examples with a large amount pf C# code in. I suspect much pf the exposed functionality will be supported. Can we assume it all will be? Can someone from Metastorm provide us with an answer to this, perhaps?

If we start assuming it is, and it changes in a future release, there will be a huge amount of broken code. Those million .net developers will be busy little monkeys...


__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
rvignerot

Member
Registered:
Posts: 23
Reply with quote  #4 
Thanks for the feedback.

In the past, this type of documentation has always been delivered in the SDK via the Scripting Developer Guide.  With Version 9 we made a change to try to deliver this type of information to our customers ealier.  Therefore, this documentation is now being delivered via the Designer User Guide.  Unfortunately, due to time contraints we were not able to complete the documentation of the new Process Object Model.  We plan to complete this documentation and to deliver this in the next release that is targeted for this May.

As Jerome says, most of the exposed functionality will be supported.  It is possible that there may be a small amount of changes in order to correct defects and to improve maintainablity, but any changes will be minor and should be easily corrected.
0
Nappy

Avatar / Picture

Guru
Registered:
Posts: 1,087
Reply with quote  #5 
How about a beta/RTM documentation program?
I'm in the position to wait for may SR1 release before taking a serious look but a lot of people are diving into the product.
They would probably be helped with "last build" documentation and they would probebly be able to help you develop the docs by finding errors early
of course with a big disclaimer on top "WORK IN PROGRESS" ;)

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.

PS that's for V6/7 for V9 the problem is V9 at the moment ;)
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!