How does a custom request table create a task on a custom task table

[Blaze2]

First time creating a table where a request will come from and a subsequent task.

Normally it is just the table for the application I am creating for, so please forgive me for my ignorance.

Here is the scenario.

I created two tables

u_blaze_requests

u_blaze_tasks

I have numbered them BR and BT respectively.

How would I get a Request created from "BR" to create an "BT".
I am playing around in my personal instance and for the life of me can't understand the logic.

All I am able to accomplish is creating the BR and then it creates an RITM.

Any Help Would Be Appreciated

[Blaze2]

Good Question.
The customer wants a table separate from Request.
I wanted it to look the same as request though, so I just extended the Request table.

Ideally, I want to create a Blaze Request numbered as BR0012345 and then create a "RITM" numbered BT0012345

Even if I extend Task, it will have completely different Stages etc from Request, so I will still need to have the custom table populate under

Workflow Editor > Check Out WorkFlow > Properties > General > Table = u_blaze_request

[antin_s]

When you say you customer wants a table separate from Request, does it mean that they dont need any functionalities of   OOB 'Request' table? If that's the case, why do we need to extend 'Request'?

[Blaze2]

We don't need to extend Request.

The requirement was to have it create a unique identifier.

So I extended request, simply so that it would have the same fields as the request form, without having to do any of the configuration for it.

I have it as a record producer now, where it creates the required BR0012345. but there is no creation of the "RITM" or BT0012345.

This is what I am trying to solve for At the end of the day, I would still need my custom Tables name to populate in the Workflow Properties, so that my stages and tasks could be created.

[Blaze2]

On this table, I don't have the same exact fields as on the Request form. Several of those fields were not needed.

I also am creating unique numbering, notifications, stages, and states

[antin_s]

If it is all about creating the BT, i wouldn't recommend extending from Request table. Because when you extend Request, it comes with its business rules, workflow..etc, which you may or may not want.

You may create the table(u_blaze_request) without extending ''Request', and create an 'after' Business Rule to create records 'u_blaze_task'

Hope this helps. Mark the answer as correct/helpful based on impact.

Thanks

Antin