adamw

Yep, that's already added. There's a refresh button you can press, as well as a new preference that allows you to set an auto-refresh time. (Min 60 seconds)

Can SIMS export this data out, in the same way that you can do for teacher cover lessons?

Hey Eric, Just to follow up what Syed said, I'll make sure that the guys who deal with our third-party integration see this. Also, if you haven't done so already, and adding this to the ideas portal should help it gain some traction.

Hi there, Sorry about the delay in responding. Just to let you know that I've pushed this under the nose of our MIS developers here and they are aware of it. Currently we don't export that data from SIMS, but it is something to bear in mind for the future. In the meantime, I'm wondering if there is another way we can get this information into your platform, perhaps by some cleaver use of FrogCode? @Graham Quince

Hey guys, As some of you may already know, I'm looking to make some improvements to the notice board widget. One of the things I have been looking at doing is changing the permissions needed to create / edit and delete notices. My current thinking is this: If you are admin of a site, you can do everything - add, edit and delete all notices. If you are not admin, but have contribute rights, you can add, edit and delete only notices posted by you. If you have view rights, you get no add, edit, delete controls - only the ability to read notices. I think this should cover most use cases, but any feedback would be appreciated. Finally, if you have any other things you'd like to see done with the noticeboard then now's the time to speak up! I've already had a list of stuff from @Graham Quince which I am looking into and I will be checking the ideas portal as well. We can't promise to do everything all at once, but hopefully we can introduce some incremental changes over time to improve the widget. Thanks!

Probably I'll look into it.

FDP stands for Frog Developer Platform. Basically It's a set of API's (ways of requesting data from your Frog system) that are available for you to use. The easiest way is to use these endpoints is via either a HTML widget, or using FrogCode. You create a request to one of these endpoints in Javascript, pass some parameters and will get a data response back. Your widget then can use this data in whatever way it needs. For example, you may want to get some user data from the system, so you'd make your widget request data from the fdp/user/get endpoint, I'm pretty sure that @Graham Quince has a stash of tutorials floating around if you wanted more information

Personally, I wasn't aware there was a problem with students losing data from text-activity widgets. I'll have a word with @Graham Quince and see what the score is. To answer your question - this is separate from that, so wouldn't affect it.

@deanmoulder in the next release we have added class-goals to the "Continuum Progress Summary by Assessment Period" report and the "Student Progress Summary by Assessment Period" report. Hopefully that will be useful to you

Hi Chris, Possibly in the next release (don't hold me to it) - we've added a new FDP datastore endpoint - that lets you do as you have specified - add, edit, delete, retrieve data on a per user per widget basis. The backend parts of it were added as part of another project, but I thought that people may like this functionality, so I added some new FDP endpoints. We need to wait for that to be released before that becomes available to you. Having said that, there's nothing stopping you saving this data to your own servers, and retrieving it as required. The FDP endpoints should make your life easier though - when they are available.

Sorry about that! I'll have a look into it asap, I'm currently smashing my face against the notice board widget. Gotta get in all those shiny new features!

This doesn't sound right. I've had a word with our MIS guru and he's fairly certain that we pull out whatever is marked in SIMS as the parents 'primary' email address. Since the email addresses are already in Frog, we know that the extract is working. There should be no reason why they don't update. He's going to look into this and see if there's an issue that we're currently unaware of. I'll get back to you if he manages to dig anything up.

I'll see if it's possible to squeeze that in now - If not, I'll add it to the backlog to be done for the next release.

Coming soon! Rich text in notices and forums: Notices: Forums: Should work like the rich text editor in the text widgets.

This could certainly be done via a FrogCode widget. You would need your data stored on a server somewhere that your FrogCode app can access, but it doesn't sound like a super hard problem. The hardest part will be getting the data back from your server. the rest is just some display code. This sounds like one for @Graham Quince

Hey there, Sorry for taking so long to get back to you. We're swamped here at the moment! Getting all those new shiny things into Frog The only way I can think to do this, is to create a new group called 'Teaching Staff' - get that groups UUID, and then use that in the api request. This will then bring back the group members for that group. You would have to manually maintain this group however. I was also looking into if you could do this via the group leaders (it's possible that the group leaders are teachers, but you'd have to get all groups out, all members then search for leaders.... it would be a pain, and not at all performant (and I haven't tested it, so it may not work at all). I'll have a look to see if it is possible to add something in the future that will allow us to get 'allgroupleaders' or something like that. It's possible that will get you closer to what you want. Unfortunately there's no way currently to split that down further into year groups - we simply don;'t have that data available in the system. I'll keep thinking about this, and will update you if I get a better idea.

Same in Frog Learn I think, I think @Sam Brown was talking about the usernames. So the display name would update, but the usernames wouldn't. If they don't use the users surname in their username then this wouldn't be a problem - if they do, then a CSV import would be needed to fix them the first time.

Hi Paul, It looked like one of your DNS servers in school stopped responding and that's what caused the issue. You should be getting a response to your ticket which will contain the specifics of what the issue was

Hi Paul, I had a word with our systems guys this morning, and it looks like there was some DNS problems that have now been resolved. Can you let me know if you are still having the problems you mentioned?

That's correct See Grahams response above. Currently you can't rename the zip files, otherwise it causes problems. We'll look into making sure this isn't a problem in the future! Glad to hear that everything is working now.

Hi Ann, Everything should be working again after we removed the problem widget, can you confirm

This is a bit odd. Did you try and 'deploy' the package from the frog-code editor?

Which page have you used this widget on? I'll log in to your platform and have a look for you. I can't see any reason why this would break anything though, so the problem you are having is quite strange!

Hey Ann, I've just sat down with @Graham Quince and we've sorted this for you. The issue is that you needed to use your own package ID and widget names etc, and not the ones in my example - we've updated your widget so it works now! Sorry, I should have mentioned not to use the same ID's as in my file If you refresh your platform and check the widget now, it should work. Then you should be able to customise it how you want it. Remember, you'll need to add a select user widget to the page when you come to preview it! Hope this helps!

Hey Ann, I put together a quick and dirty widget that should do the job. It has zero formatting and style - that could be added later. It should give you a good starting point. And if you ask @Graham Quince nicely, I'm sure he'll help out! It doesn't look like much, but it does the job When you select a user it will find the reg-group for that user and display it below. If it can't find a registration group it will display a nice message about them not having one. Should get you started. Widget.JS Com.Frog.Utils.require( '//package/widgets/7BF661392001B4AA9D22EF07A135500A0EA17A0C6D1D5598/assets/styles/main.css', '//package/widgets/7BF661392001B4AA9D22EF07A135500A0EA17A0C6D1D5598/assets/views/main.ejs', '//package/widgets/7BF661392001B4AA9D22EF07A135500A0EA17A0C6D1D5598/widget.ejs', '//package/widgets/7BF661392001B4AA9D22EF07A135500A0EA17A0C6D1D5598/models/registration.js' ).then(function() { Com.Frog.Controllers.Widget.extend('Widget.RegistrationGroup', { }, { prefs: {}, selected_user_uuid: null, packageID: '7BF661392001B4AA9D22EF07A135500A0EA17A0C6D1D5598', /** * Constructor. Runs when the widget is first loaded. * * @method init */ init: function() { //default to the current user to start with this.selected_user_uuid = FrogOS.getUser().uuid; this.render(); }, /** * Udate the selected user and re-render the widget when a new user is selected. */ 'broadcast.selectedUser': function(el, ev, options) { if (options.model.attr('uuid') === this.selected_user_uuid) { return; } this.selected_user_uuid = options.model.attr('uuid'); this.render(); }, render: function() { if (this.selected_user_uuid === null) { return; } this.showLoader(); var params = { identity: this.selected_user_uuid, group_type: 'registration' }; Widget.Models.Registration.getGroupsForUser(params).done(function(reg){ var reg_group_name = 'No Registration Group Found'; if (reg.length > 0) { reg_group_name = reg[0].name; } this.element.html( this.view('main.ejs', { registration_group_name: reg_group_name }) ); }.bind(this)).always(function(){ this.hideLoader(); }.bind(this)); }, /** * Event fired by the Site Controller. * * @event 'widget.live' */ 'widget.live': function(el, ev, data) { this.render(); }, /** * Event fired by the Site Controller. Tells the widget that the site is in Edit Mode. * * @event 'widget.edit' */ 'widget.edit': function(el, ev, data) { this.element.html( this.view('./widget.ejs') ); }, /** * Event fired by the Site Controller. Tells the widget that something has been changed during editing. * * @event 'widget.updated' */ 'widget.updated': function(el, ev, data) {} }); }); models/registration.js Frog.Widget.Model('Widget.Models.Registration', { getGroupsForUser: function(params) { return this.api('groups.getFor', params, { "dataType": "json registration", "type" : "GET", "converters": { "json registration": function( res ) { var reg = Object.values(res.data); return Lib.Models.Group.models(reg); } } }); } }, {}); assets/views/main.ejs <div data-name="Widget.RegistrationGroup" class="widget-content"> <div class="registration-group-content"> <%= registration_group_name %> </div> </div>