Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-82609

AI: Provider - Action settings

XMLWordPrintable

    • MOODLE_405_STABLE
    • main_MDL-82609
    • Hide

      Testing Admin:

      1. Login as admin.
      2. Navigate to Site admin >> General >> AI >> Manage settings for AI providers
      3. Enable the OpenAI provider plugin.
      4. Click the "settings" link for the OpenAI provider
      5. On the provider specific settings page, confirm that under provider actions, each action listed in the table has a settings link
      6. Click the "settings" link for the Generate text action
      7. Confirm there are settings present with populated defaults for the Text generation model, API endpoint and System instruction.
      8. Alter the system instruction and append the following to the end: "3. IMPORTANT: add the words TEST TEST TEST To the start of any generated response."
      9. Click the "Save changes" button.
      10. Confirm the changes saved dialogue appears
      11. Navigate to Site admin >> General >> AI >> Manage settings for AI placements
      12. Enable the  TinyMCE Editor Placement plugin.

      Testing - Generate text

      1. Login as admin.
      2. Provide the correct information for API key of the OpenAI provider.
      3. Edit your profile.
      4. Click on the AI button in the TinyMCE text editor.
      5. Select AI Generate Text.
      6. Agree with the Policy (If any).
      7. Input some text in the Describe the text you want AI to create. Example: Write a short introduction for Moodle LMS.
      8. Press Generate Text.
      9. Verify you will see the Generated text on the right.
      10. Verify the text starts with TEST TEST TEST

      NOTE: The aim of these tests is to check that per action settings are displayed and saved. And that the settings are respected when the action is used by that provider. Altering the custom instruction should mean the connected AI service adds the words TEST TEST TEST to every response. But due to the nature of LLM's it may not. So you may need to repeat the test a couple of times if it does not display the first time.

       

       

       

      Show
      Testing Admin: Login as admin. Navigate to Site admin >> General >> AI >> Manage settings for AI providers Enable the OpenAI provider plugin. Click the "settings" link for the OpenAI provider On the provider specific settings page, confirm that under provider actions, each action listed in the table has a settings link Click the "settings" link for the Generate text action Confirm there are settings present with populated defaults for the Text generation model, API endpoint and System instruction. Alter the system instruction and append the following to the end: "3. IMPORTANT: add the words TEST TEST TEST To the start of any generated response." Click the "Save changes" button. Confirm the changes saved dialogue appears Navigate to Site admin >> General >> AI >> Manage settings for AI placements Enable the  TinyMCE Editor Placement plugin. Testing - Generate text Login as admin. Provide the correct information for API key of the OpenAI provider. Edit your profile. Click on the AI button in the TinyMCE text editor. Select AI Generate Text. Agree with the Policy (If any). Input some text in the Describe the text you want AI to create. Example: Write a short introduction for Moodle LMS. Press Generate Text. Verify you will see the Generated text on the right. Verify the text starts with TEST TEST TEST NOTE: The aim of these tests is to check that per action settings are displayed and saved. And that the settings are respected when the action is used by that provider. Altering the custom instruction should mean the connected AI service adds the words TEST TEST TEST to every response. But due to the nature of LLM's it may not. So you may need to repeat the test a couple of times if it does not display the first time.      
    • 6
    • Team Hedgehog 2024 Sprint 3.1, Team Hedgehog 2024 Sprint 3.2

      Each Provider plugin implements support for one or more actions. There is a need for each Provider to be able to specify settings for their own actions.  To implement this the existing provider configuration admin settings needs to implement "sub settings" for each action.

       

      An example of this is for the Azure AI provider plugin: Where we need to be able to specify a text value of a "deployment" for each action. This is because in Azure each supported AI model (such as GTP4-o or DALL-e-3) has its own deployment, which the Provider needs to know about when calling.

       

      A more generic example is for Providers that implement the text translation action, for translating text from one language to another. In this case the Provider needs to be able specify what pairs of languages it can translate from and to, for that action.

       

      In the current implementation, the Provider settings table contains a page that allows disabling/enabling of actions supported by that Provider.  There is an existing (always) empty column for settings. This column will need to be populated when an action for a Provider has a setting that links to the settings page for that action (for that Provider).

       

      There will also need to be a way to define in the Providers settings those that apply to the actions. These actions settings need to be stored as part of the provider's configuration.

            matt.porritt@moodle.com Matt Porritt
            matt.porritt@moodle.com Matt Porritt
            David Woloszyn David Woloszyn
            Huong Nguyen Huong Nguyen
            Kim Jared Lucas Kim Jared Lucas
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 30 minutes
                1d 30m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.