Automation - 'On The Fly' Filters

We are looking at ways that we can automate the reporting side of gINT for our users.  Is there any way of being able to expose the filter options to the user during the process (I assume this would be a script of some variety)?

We would like the users to be able to select exploratory holes based on a) Site Area, b) Phase of Works, c)Specific Holes for Output.  a) & b) are fields from the Point table.

Looking at the explanation of scripts in the advanced output tutorial it seems to imply that the output settings have to be predefined - holes to include being one of them.

We would also like it to be able to select the correct log template based upon the hole type. 

  • Hi Paul

    A script doesn't need the Keyset values (PointID) defined, and it can take filter settings.

    You can create a PointID Output Condition in the report properties to stop a TP hole type printing on the Borehole report.

    The Datgel Output Tool Add-In may help with your automation goal. It allows you to save output configurations of many reports and run them as needed.

    cheers

    Phil

    Phil Wade
    Datgel
    Bentley Channel Partner and Developer Partner
    E: phil.wade@datgel.com | T: +61 2 8202 8600 & +65 6631 9780

    Get the most out of gINT with Datgel Tools.

  • Hi Paul,

    Adding on to what Phil said, you can set up gINT Scripts to accept user input, and you can also store Filter options using the "Filter" Spec. So, yes, you certainly can use scripts to simplify and automate reporting for your users.

    There are a number of examples in gINT Help. Look under Contents>How-to Guide>Command Scripts and Contents>Scripts. The articles "Command Scripts - Output (how-to guide)" and "Command Scripts - User Input Parameters (how-to guide)" will be of interest.

    You can also create gINT Rule Add-Ins to generate and run gINT Scripts which offers even more power and flexibility for automated reporting. Feel free to contact me directly if you'd like to discuss further (jesse.greenwald@bentley.com).

    Regards,
    Jesse