This is part 5 in the series about creating Workbook plugins for Profitbase InVision.
Part 1 : The Basics
Part 2 : Reading data using the Sql Script Web Service API
Part 3 : Writing data using the Sql Script Web Service API
Part 4 : Publishing events to the Workbook
Part 5 : Conditional execution of GenericAction (this one)
Download : Source code and sample database
In this post, we’ll walk through how to configure what to do when the GenericAction of a plugin is called.
This is part 4 in the series about creating Workbook plugins for Profitbase InVision.
Part 1 : The Basics
Part 2 : Reading data using the Sql Script Web Service API
Part 3 : Writing data using the Sql Script Web Service API
Part 4 : Publishing events to the Workbook (this one)
Part 5 : Conditional execution of GenericAction
Download : Source code and sample database
In this post, we’ll walk through how to publish events from a plugin, so that other components in the Workbook can react and do their thing.
This is part 3 in the series about creating Workbook plugins for Profitbase InVision.
Part 1 : The Basics
Part 2 : Reading data using the Sql Script Web Service API
Part 3 : Writing data using the Sql Script Web Service API (this one)
Part 4 : Publishing events to the Workbook
Part 5 : Conditional execution of GenericAction
Download : Source code and sample database
In this post, we’ll walk through using the Web Service API of InVision to write data to the database. As I mentioned in Part 1, InVision is built using AngularJS, so some experience with that framework is required.
This is part 2 in the series about creating Workbook plugins for Profitbase InVision.
Part 1 : The Basics
Part 2 : Reading data using the Sql Script Web Service API (this one)
Part 3 : Writing data using the Sql Script Web Service API
Part 4 : Publishing events to the Workbook
Part 5 : Conditional execution of GenericAction
Download : Source code and sample database
In this post, we’ll walk through using the Web Service API of InVision to read from the database. As I mentioned in Part 1, InVision is built using AngularJS, so some experience with that framework is required.
In this short series, we’ll walk through creating a simple Workbook plugin.
Part 1 : The Basics (this one)
Part 2 : Reading data using the Sql Script Web Service API
Part 3 : Writing data using the Sql Script Web Service API
Part 4 : Publishing events to the Workbook
Part 5 : Conditional execution of GenericAction
Download : Source code and sample database
Profitbase InVision is built using AngularJS (1.0 right now), so some experience with AngularJS is required for building plugins.
You can download the source code and sample database for this demo from the link above. I won’t talk about how I built the UI since there’s nothing InVision specific about it, it’s just standard HTML, CSS and AngularJS.
This is the fourth and final post in a series focused on Data Flow development.
Probably the most important tool used while developing software is the debugger. The debugger lets you step through your code and inspect the state of your program during runtime, so you can see what’s actually going on.
This post will focus on how to debug your custom class libraries while they are being executed by the Profitbase InVision Worker. For information on how to deploy your assembly (build and copy to target folders), you should read Part 1 of this series.
With InVision 2.0, we’ve also created a tool for upgrading the system model (model schema and solution metadata) from one version to the next. The Model Version Tool (MVT for short), enables you to incrementally upgrade the system model from its current version to any version supported by the tool (no, you can’t downgrade after an upgrade).
With Beta 3, the primary focus has been on adding support for charting using Highcharts. There are still some work left to be done before this feature is 100% complete, but it’s pretty stable and you should be able to create great looking charts.
This is the third post in a series focused on Data Flow development.
In this post, we’ll continue using your Data Flow from Part 2, but instead of executing it from the designer and hard coding the message we’re writing to the database, we’ll create a Workbook with a text input field for entering the message.
This is the second post in a series focused on Data Flow development.
This post will show you how to create a parameterized Data Flow Item and execute it in a Data Flow. It’s a follow up to Creating and Deploying a custom Data Flow Item Class Library, so we’ll use the class library we created there. The way parameters are used, however, is exactly the same whether we use our own custom library or a built-in library.