Property was changed back to modules as it was decided that exposing a
list of modules enabled would be more useful than the opposite.
This reverts commit 3e43b4dde9.
* Do not delete user vmbox, and use common functions to get main user vmbox
* Adjust flow at usersRenderVMBox + add TO-DOs
* Create or update user vmbox when enabling feature
* Refactor to reduce nesting & repeated code/checks
* Refactor + check user's vmbox in main callflow modules
* Fix variable name
* Create function to extract data from callflow flow
* Receive main user callflow, and other user callflows, at usersFormatUserData
* Get vmbox from main callflow if possible
* Undo unnecessary changes & remove unused function
* Get user vmbox from main callflow
* Get vmbox only when needed + add TO-DO's
* Undo refactored code not related to bug
* Changes to support usersMigrateFromExtensions case
* Get main vmbox for feature popup render, and restore add vmbox logic
* Add missing self variables
* Update VMBox status in user main callflow
* Clean code
* Fix some names
* Use usersGetMainCallflowAndVMBox to get bot callflow and vmbox
* Remove unnecessary change
* Remove unnecessary call to API
* Multiple small fixes
* Fix callflow module name on check
* Change property name to skip callflow module
* Fix defaultValue when extracting data.skip_module
* Fix vmbox active value
* Fix to get vmbox active status, when callflow module is not present
* Hide device form on user creation if there aren't provisioners
* Prevent request if there no provisioner API
* use appFlags to looks for valid provisioner
* Remove this
* Don't store device data inside user data, on user creation
* user creationg, prevent device error
* Revert "Remove this"
This reverts commit 7102cf9b4a.
* Remove this
* Update add user modal to show labels instead of icons
* Fill brand field on add device section
* add device form
* Save user device
* Binding form events from single function
* Add extra button Create User and Add Device
* Code style
* Create user and device form based on mockup
* Handling form validation
* Create User and Add another button
* Revert "Remove this"
This reverts commit 7102cf9b4a.
* Styled notification email
* Use single chosen field to select device model
* improvements
* Improve form validation message
* Delete unused template
* Code style improvements
* Fix typo on lodash flatMap statement
Device family as argument
* code style improvements
* Create function to render add user modal
* Handle error on user creation to prevent form buttons state
* Render users list without auto scroll when save and new btn is clicked
* Fix device data validation
* Rename view for vm_to_email feature
* Modify feature dialog to display vmbox and vm-to-email functionalities
* Refactor save function for user's vmbox feature
* Change voicemail feature headline and title
* Create function to add main VMBox to user + other helpers
* Improve functions related to get formatted user numbers data
* Complete function to add vmbox to user
* Add function to delete user VMBox
* Remove old usersRenderVMBox code
* Extract form validation from `monster.waterfall`
* Use vmbox data from feature load function
* Get user's VMBox on feature save
* Handle VMBox feature
* Add missing self variable
* Get main user vmbox, match user list with vmboxes, and code refactor
* Code and logic fixes
* Set vm-to-email disabled if vmbox is not created for new user
* Add delete_after_notify to new voicemail box, and related TO-DOs
* Update ID and class related to vm_to_email_enabled option in vmbox view
* Reorganized new functions
* Get full main vmbox for user on feature load, and patch vmbox function
* Add parameters to JSDoc comments for patch functions
* Reduce API requests when adding vmbox to user
* Remove double check at usersGetMainCallflow
* Code fixes
* Remove translations that are no longer needed
* Use object instead of parameter list for function usersDeleteDialog
* Refactor user deletion methods, and subscribe to new user deletion event
* Remove user deletion and related unused functions
* Use common event to delete user
* Remove user deleteDialog and related data
* Rename deleteSmartUser dialog event
* Add checkbox to create vmbox on user creation form
* Use waterfall flow for user creation
* Extract user create api call to new function
* Create vmbox only if requested
* Rename view data property to create vmbox
* Fix waterfall callbacks for user creation flow
* Add translations
* Refactor code and remove vmbox from callflow
* Do not show VMBox row field if there is none for user
* Do not create VMBox at usersSmartUpdateVMBox, if user has none
* Add gittatributes to use default line ending behavior
* Apply suggestions according to code review
* Code refactor according to review
* Conditionally show the buy numbers action for groups
* Conditionally show the buy numbers action for users
* Conditionally show the buy numbers action for strategy
* Only allow user type update if different from original
* Clean up user type assignment on user update
* Clean-up user type assignment on user creation
* Move sub-module templates in their own `views` folder
By using `getTemplate()` we can specify which sub-module a template is
related to, enabling this behavior.
The templates names were shortened by stripping the name of their
sub-module from it since they are stored under their sub-module folder.
String templates are created using `getTemplate()` instead of
`monster.template()` that we are trying to depreciate.
* Only use `getTemplate()` for both regular and string templates
* Allow toggle via config between two caller id selection methods
This only affects caller ID for users. If
monster.config.whitelabel.allowAnyOwnedNumberAsCallerID is falsy, the
old way of assigning caller ID will be activated i.e. users can only
have their caller ID set to numbers assigned to them, otherwise the main
number is used. If monster.config.whitelabel.allowAnyOwnedNumberAsCallerID
is truthy, the user can also have any number owned by the account used as
their caller ID.
* Add automatic eslint fixes
* Eslint fix: make mixed user of && and || tidier
* UI-2757: Add context to change users passwords
* UI-2757: Add a confirmation field to check new password
* UI-2757: Set validation in code instead of markup
* UI-2757: Disable button once clicked to avoid click bomb
Joris Tirado
Guillermo Gutiérrez
Ricardo Merino
sergey-safarov
mira-t
Jean-Roch Maitre
Anthony Perish
Joris Tirado