Workflow Builder

At first we understood that Creating standards for construction documents. Let's get one (1) thing and use it in every project. It's probably a good thing. Because every project will share the same standards. So we started by starting development with our friends. We are grateful to ProjectsAsia Limited; Khun Howard, Khun Niyom, and Khun Tulya (Puay) very much for giving useful information and developing together until there were 3 projects that came to try out. (Even though I didn't use it until the end :) it was a very good experience.

We went to work on national projects. which even though it is a country that is not very large But it allowed us to get to know FIDIC and get to know people with experience from many fields. Building an airport is quite complex. This one, Mr. Kong (currently Thai Obayashi) has given us quite a lot of knowledge.

A lot of things have changed there. They don't call supervisor cm like we do, they call it cs - construction supervisor. Just changing the name of the role caused a lot of damage to our business logic - we learned what hard code is.

There are more things than SI, PMI. Engineer Instruction is added. The raft breaks when The Engineer can create documents himself. On the other hand, Engineer representative You can create it too. We think there's more variety. There is both sending to multiple parties. Each party may not answer at the same time (Fan-out) many things, which makes our Linear workflow unusable.

After working on the workflow of documents in construction many times, I began to think that A system for custom workflow is quite necessary. If we want to expand the market in Small projects where the owner doesn't have all players, or may be so large that there are more players than we write in the code, this thinking is about dividing the structure to include both Many things go together.

• State - I really like this because the user can determine which state is start, end, or even fanout (that is, documents sent out to many parties, many people).
• Regarding transition - it can be specified that the option for approval or rejection can be selected. Importantly, we include the SLA- Service Level Agreement so that we can specify what the maximum period (days) for decision-making should be.

• About the fields of each document itself - when creating a document, what fields will be found. This includes fields that are attachments and photos in inspection.

• These items will be displayed in Stepper to tell the user which parts of the document have been reached.

When it came out like this So it became easier for us to customize document workflows to suit every job. It prevents us from being a problem for customers in many matters, and the bugs are reduced quite a bit.

For those who have tried using or setting it up and have feedback, we also have a feedback menu for sending additional comments as well.