Profile

Cover photo
16 followers|34,425 views
AboutPostsCollectionsPhotosYouTube

Stream

Quandis

Shared publicly  - 
1
Add a comment...

Quandis

Shared publicly  - 
 
A quick overview of creating a new workflow in QBO3.
1
Add a comment...

Quandis

Shared publicly  - 
 
The ExcelEngine plugin now supports transactional imports with rollbacks.

Assume you have a spreadsheet with 1000 rows, each of which is supposed to create a Foreclosure, Loan, Property, and launch the appropriate Matrix-driven workflow for the Foreclosure.

If 3 of the rows encounter an error when launching the workflow, all changes caused by the rows in error will be rolled back, essentially removing the Foreclosure, Property and Loan.

Note that for this to work, you need to include the following in your qbo.Default connection string:

MultipleActiveResultSets=True
1
Add a comment...

Quandis

Shared publicly  - 
 
Workflow steps are often used to create tasks and documents. Now you can specify additional parameters when creating templated items. For example, you can specify custom fields in a task, or a status or type in a document.

This allows power users to re-use tasks and documents across workflows, and provide for more targeted reporting.
1
Add a comment...

Quandis

Shared publicly  - 
 
Less is indeed more
 ·  Translate
Wie Tabellen eigentlich aussehen sollten: 
1
Add a comment...

Quandis

Shared publicly  - 
 
Thoughts on node.js

One of our team members pointed me to a nice marketing pitch for node.js. It begot an interesting conversation about node.js vs. Java, C#, etc. In the interests of full disclosure, I love javascript, but have only dabbled in node.js.  Our software platform is built on a Microsoft stack, so we're C# server-side.

It strikes me as likely that the performance benefits seen by companies adopting node.js derive from three things:

1. Forcing a developer to think (and code!) in an asynchronous manner, 
2. Using the same language client and server-side reduces developer learning curves (and possibly troubleshooting),
3. The prototypical inheritance lending flexibility in architecture; passing callback functions around is more convenient that traditional callback structures in Java or C#

A practical question for Quandis is whether to adopt node.js or not. I have trouble justifying that move for a few reasons, some good, some bad:

1. Forcing developers to code in an async manner is a fundamental requirement, regardless of language. Today's C# make is ridiculously easy to use on-the-fly delegates like js.

2. The .NET Task Parallelization library is really slick, and I've not seen any equivalent in the node.js world (please point me to examples if you know of any).

3. Generics gives me a nice blend of abstract flexibility with compiler enforcement of concepts I deem necessary; I've not found the same in the .js world.

4. Reflection is really, really useful.

With that said, node.js is worthy of serious consideration simply to facilitate a migration from Windows to Linux to save on our data center costs. My fear with such a move is that we have people on our team that are really knowledgeable on the MS stack, and we'll have to rebuild that knowledge base on a Linux-based stack. That labor effort may well outweigh the licensing costs we save. With node.js, at least we can bring our js expertise to bear!

Let me know if my minimally-educated assumptions about node.js that are off base!
1
Add a comment...
Quandis's Collections
Story
Tagline
We automate; you profit.
Introduction
Quandis Business Objects combines completely web-based CRM, document management, accounting, modelling, and workflow in a single integrated suite.
Contact Information
Contact info
Phone
949.525.9000
Email