creating an object with several activated tabs in one go

Hi,

Currently, when working with FD's UI to add an user entry, you can choose to activate several tabs. Then, when pressing "ok" , if any tab's mandatory fields is missing or isn't well formated the system would tell.

Now let's look how it works with the webservice: you have to create the user entry first (User tab), then you can activate another tab and set its attributes by issuing another request. This is kind of sloppy in some context. Let's imagine we want to create an account with a mail attribute with the webservice.

1. account creation
2. activate the Mail tab.

If anything wrong happen with the second step, depending on the context you may have to deleted the account. Add to that that during a certain period of time, the account is somehow made "available to the world" with no email. Overall you also have to handle several errors handling in sequence...

So I think the webservice should implement a way to activate several tabs in a way so you get all the errors/mandatory fields in one go.

Let's discuss.

(from redmine: issue id 4799, created on 2016-05-20, closed on 2016-05-30)

• Changesets:
  • Revision f422bc2f by Côme Chilliet on 2016-05-24T09:16:31.000Z:

Fixes #4799 setfields can now take several tabs at once

• Revision f0d4cb1d by Côme Chilliet on 2016-05-24T09:19:19.000Z:

Fixes #4799 setfields can now take several tabs at once

• Custom Fields:
  • Bug in version: 1.0.12

hello,

first code is in, plese test it

Cheers

(from redmine: written on 2016-05-26)

Well, Côme is informed of the current state of my testing. It led to #4805 (closed). Basically we are close to it.

(from redmine: written on 2016-05-27)

hello,

informing come is nice, but putting a status in the ticket is better :)

so i'am putting in solved waiting for come input

Cheers

(from redmine: written on 2016-05-27)

informing come is nice, but putting a status in the ticket is better :)

There will always be something "better" to do, isn't it ? :)

And #4805 (closed) hasn't been linked to the current one when it has been initially created. Would be nice to have it so.

(from redmine: written on 2016-05-27)

#4805 (closed) is a separate issue, closing this as I expect if it did not work you’d have said so. We need to close tickets as issues are addressed to keep track of what is done.

Close issue

(from redmine: written on 2016-05-30)

It all depends on what you consider "done". Indeed you can now create in one go but still, it has a linked bug (to me). This being said, do as you like. Cheers,

(from redmine: written on 2016-05-30)

closed

added Changed label