BSV_VERSION

hpl123

Hi support,
I saw in the changelog the new update with the new BSV_VERSION function but when i try to use it in an tag expression it doesn´t work. Am i missing something?
Thanks

aware_support

Where is the tag expression used?

hpl123

I am trying to use it in a HTML file imported to AIM as a footer. The expression i use is: <<BSV_VERSION>> (the full line of html is: "Version: <<BSV_VERSION>> |". In my application i see "Version:" only and nothing more.

I have other expressions working in the same file.
Thanks

aware_support

First of all, you need to use it like this: <<BAS_VERSION()>>

Second of all, if you want to use it tag expressions outside of reports/presentations/documents (such as footer as in your case) you will need an attribute to store its value (for example, in SystemSettings) and a rule to calculate the value: SystemSettings.BSVVersion = BSV_VERSION()

Tag expression then needs to show the attribute

hpl123

Ok thanks. Will try this.

hpl123

Still having some problems.

Here is what i have done:

Created a attribute (plain text, calculated checkmark ticked) in the SystemSettings BO called "BSV"
Created a rule in the SystemSettings BO "SystemSettings.BSV=BSV_VERSION()"
Added tag expression to my html file: "<<SystemSettings.BSV>>"

Nothing is displayed in my html file but if i open up systemsettings when logged on as a user i see a calculated value (1.64). Have i missed something?
Thanks

By the way, i noticed something. The calculated value was not the BS version (1.1 in my case) but it was 1.64 and the 64 representing how many times i have set this BSV to "Test". Is this the intended behavior?
Thanks

hpl123

All OK, my html editor had messed up my html file. I rewrote the entire tag expression and now it works.

I still wonder though about my second question in my previous post.

Thanks

hpl123

hpl123 wrote
Created a rule in the SystemSettings BO "SystemSettings.BSV=BSV_VERSION()"

I also added this rule in a initialization process

hpl123

To clarify,

If i use the steps previously mentioned in this post (steps i outlined), every time i use this tag expression in a BSV in development i.e. a BSV that i work on and then test etc. the tag expression (BSV function) displays/reflects the number of times i have set the BSV to test (e.g. 1.64).

When i use the exact same steps on a published BSV it works as it should and the tag expression (BSV function) displays/reflects the correct/actual version (e.g "1.1").

Is this the intended behavior? Now it works and i´m pleased, just curious about the behavior. Thanks and sorry to be bombarding you with posts 🙂.

ACDC

One of the problems I see with this feature is that your BSV version could changes to 1.2 again . The changes occur when you re install the Server or move to another server where you recreate your development environment and re import your BSV....and this does happen !

There is no mechanism in place to start your BSV version at a particular version no. and then import your backed up BSV (unless you roll over the newly created version until you get to your current version number)

One of the ways around this is to embed the BSV number into the exported BSV and then when importing the BSV prompt the user if they want to maintain BSV version numbers. This way when the imported BSV is carried out, it will take on the new BSV version number from the imported BSV file rather than start at 1.0 again

Does that make sense ? if so then maybe support could add this feature to the wish list for better version control

hpl123

Good point, having this option would be useful.