Hi @moondory77 ,
The work on this is running in our development environment. The Builder API support is in place - and we're currently looking at the possibility of adding it as a new tab in the Deployment screen of the Portal.
Paul.
Forum wide moderators
Hi @moondory77 ,
The work on this is running in our development environment. The Builder API support is in place - and we're currently looking at the possibility of adding it as a new tab in the Deployment screen of the Portal.
Paul.
Hi,
Apologies for the slow response.
We don't have any calls that could directly handle a "file" of profileIds. We do have a few "toBatch" calls that are callable from S2S though - so you could probably have an offboard system make those calls - and call braincloud to send the notifications in batches.
Where are these profileIds coming from? An offboard analytics system of some sort?
To answer your questions:
I hope that helps to clarify things,
Paul.
Hi @moondory77 ,
We hear you - and are looking to see what options we can provide.
The thing to understand is that there are a lot of dependencies between metadata in the brainCloud system - and our deployment mechanisms work hard to ensure the integrity of the data that gets pushed. Even more importantly - it works to prevent user data from being corrupted by a mis-match of data during deployments - which is why apps are very temporarily disabled during a deployment.
These deployments normally take well under a minute and aren't much more troublesome than a common wifi interruption for clients [depends upon the client implementation though]... (note - the deployment may seem like it takes longer on the web - as there is a lot of data dependency checking to do - but all of that is done BEFORE we disable the app... which happens just for the actually data migration activity itself).
If you contact us via the support chat with your appId and the time you last did a deployment - we can take a look to see if your deployment times are above normal.
Also - we are working to provide a separate custom entity deployment mechanism - similar to what has been done for item management.
Paul.
Unfortunately, our notification templating system is very simple and currently only supports simple text notifications. It does not currently push a template id.
We do have plans to revamp the system on our "to-do" list - but it has not been scheduled yet.
We recommend folks use the "raw" template calls - they give devs the most control over what gets sent to the various notification systems.
Paul.
To answer your questions:
I'll get the devs looking into #2.
Paul.
Hi,
API calls triggered by the backend DO count towards API usage -- so using the API Explorer to make calls do get counted as API calls. So - if you use API explorer to trigger a user batch job that then runs scripts on all of your users - yes, yes that does get counted as API calls. 
Also - uploads of files to and from the portal do get counted in the file transfer costs.
Other normal portal operations - like viewing users, viewing logs, editing scripts, etc - do NOT get charged in API counts. So to clarify - using the API explorer to view a leaderboard is going to add an API count - but using the leaderboard viewer at App > Global > Leaderboards > Leaderboards does not!
To be honest - in general - usaging of the portal is negligible. You won't really notice the usage added by what you're doing in the API explorer or working through the portal. It's only if you use the API Explorer to kick off a large job that API counts would be noticable <-- as you'd expect!
I hope that helps!
Paul.
Hmm - we'll look into it. Definitely looks like it isn't hooked up to the S2S proxy properly.
Thanks for reporting this.
Hi @moondory77 ,
Yes, you observed correctly.
During the data migration portion of the deployment (which occurs after the system has done a bunch of validation and consistency checks), the system temporarily disables your app to do the actual data migration.
This is to protect the data integrity of your app - as your app's metadata, reference data and cloud code scripts are all changing underneath it. So we disable the app, make the changes, and re-enable the app.
All of this normally takes just a few seconds - though it does depend upon the number of changes being made.
I hope that helps to clarify things!
Paul.
Hi @noah,
I agree that this would be a good feature.
I've been doing some thinking on it...
What if we could restrict an S2S server to only being able to call a specific set of scripts? That way you would be in full control as to the scope of the API that you are making available.
Would that work for your use case?
Paul.
Hi folks,
brainCloud 6 with brainBot is now live!
(https://updates.braincloudservers.com/braincloud-6.0-with-brainbot-is-here-1x54Sk)
Thoughts on brainBot - or the new features in general?
We're eager to hear what you think!
Paul.