When I tried impor comments, system shows error at created cbCalendar db

At log
2018-07-23T18:24:40+00:00 DEBUG index Prepared sql query parameters : [110665]
2018-07-23T18:24:40+00:00 DEBUG index Prepared sql query being executed : INSERT INTO vtiger_activity_reminder_popup (semodule, recordid, date_start, time_start, status) VALUES (?,?,?,?,0)
2018-07-23T18:24:40+00:00 DEBUG index Prepared sql query parameters : [Calendar,110665,????,]
2018-07-23T18:24:40+00:00 INFO  VT PearDatabase ->ADODB error  Query Failed:INSERT INTO vtiger_activity_reminder_popup (semodule, recordid, date_start, time_start, status) VALUES (?,?,?,?,0)::->[1048]Column 'time_start' cannot be null
2018-07-23T18:24:40+00:00 INFO  VT PearDatabase ->TRANS Rolled Back
2018-07-23T18:24:40+00:00 INFO  VT PearDatabase ->TRANS Completed
2018-07-23T18:24:40+00:00 INFO  VT PearDatabase ->TRANS saveentity ends

I think I've asked this before, but somewhere in a thread that I can't find anymore. So here's twice then:

If I create a workflow task that updates a field on a related module, will that update in turn trigger the workflow system on the record to which that related field belongs?

Are there any plans to add calendar integration with CalDAV calendars? I would be very happy if I could switch from GCal to Nextcloud where I control most of my calendars.

I was wondering if we have something like a maintenance mode, that would disable users from being able to login (and logout already logged in users) and disable webservices, so we could do some maintenance without worrying about changes to the database being made.

Buenos días:

No sé si alguien me puede ayudar en la organización de la información

Me gustaría ordenar por la fecha de creación del más nuevo al más antiguo lo que se visualiza en el módulo cuando es seleccionado, por ejemplo en eventos, cuando accedo a ellos, me pone el primer resultado el más antiguo y el último resultado el más nuevo, y quiero invertir ese orde ¿Cómo podría hacerlo?

http://localhost/index.php?action=index&...cbCalendar

I read we can only use autocomplete on UI types 10 and 2. That's fine for newer custom modules, but in most system modules like salesorders or invoice we have more 'exotic' types like 73 or 57. What is the reason we can't use autocomplete business maps on those?

There has been a long thread about currency fields in webservice calls. The philisophy right now is that a developer should format the currency fields to a user format and send them in like that. While that seems like to correct approach for 'new inputs', where totally fresh data is input into the application, it creates more work for the webservice developer when sending existing data back into the application. This is because you receive the data in DB format, then you'd have to format it to fit your needs, taking into account the currency format of the user your webservice application uses and send it back user-formatted. If your application, like mine, uses the entire record (as it came from a 'Retrieve' call), alters some fields that have nothing to do with currency fields and sends back the entire record with only the modifications and no further formatting, you'll get unexpected behaviour because coreBOS expects the data to be user-formatted and since I didn't alter the currency fields at all and just send them back as they were they get multiplied by a million (6 decimals, right?).

While I understand this choice and can understand the use-cases in which such behaviour could be desireable, I think it can also create some extra work for the developer on the client side in certain cases. Without going into this debate, that has pro's and cons and where arguments can be made on either side, I'd like to investigate a more practical solution.

The 'convertToDBFormat' method of the CurrencyField class has the option to skip the conversion and thus just leave the value as it is. What if we implemented a 'special field' in the 'Update' and 'Revise' Webservice methods (something like '__cbws_skipcurrencyconversion') that tells the webservice methods to set this flag? This way, when you develop a client application you can safely send your fields as you received them without having to worry about converting the currency fields. This would of course mean you'd have to send ALL fields back in DB format, but I think having the choice to select one behaviour or the other would be nice.

The old mass-edit could take a long time when you edited many many records. I tried the new mass-edit on 660 records at once, and at one point I stopped to refresh the page after ten minutes. I noticed none of the records had been altered, not even the first couple of pages. Has anything changed in this behaviour? Should I just keep waiting? Is there a fixed record limit here? Maybe, when editing that many records you're better off exporting, changing and importing?

Digging through the code to so some debugging and because I want to know more about the workflow engine, I was wondering if the workflow engine uses the same entity.beforesave and entity.aftersave events as we as developers can hook into.

I can create workflow entity methods and workflow tasks. I always confuse the two, since I don't know what the difference is, conceptually. When to use one, and when to use the other? What are the main differences and why are there two types in the first place?