A bit of background info on how things work in myDBR 1.2.
In order to support myDBR installation and usage without the need for SUPER-privilege (effectively meaning that myDBR had to be run under MySQL's root-account), we did changed how myDBR fetches the procedure parameters.
In myDBR < 1.2 parameters were fetched from MySQL system table (mysql.proc). Since this requires the SUPER-privilege, myDBR 1.2 uses now the "show create procedure" call internally. This works without the SUPER-privilege, but requires that the procedures are created under same account as the myDR's admin_username (or myDR's admin_username needs to be set as root). In current MySQL, even if you grant all privileges to user on the database, (s)he is not allowed to see the procedure source code created by other user.
So if you have problems getting myDBR to recognize the parameters, make sure that the stored procedure is created under same account as you gave to the myDBR's admin. Simply use same account for all myDBR related activities and you should be fine.
This affects only MySQL, in SQL Server we can use standard system tables for this.
We'll add a check and a proper notice to user in the next myDBR release in case of the missing privileges.
Hope this helps,