Just saying that “Something isn’t working” provides no information allowing us to help you.
You need to post the code that you are trying, along with a description of what’s happening, including any error messages that you may be receiving.
Also, regarding your latest post here, you are correct. Likewise, you don’t need to use Django at all. But if you’re going to use Django, you might as well learn how to use it properly, along with gaining an understanding of how it works.
If you’ve got no data at all associated with these buttons, then no, you don’t need a full form. I’d create the two buttons using the formaction attribute in each to link to two separate views - each of those views would take the appropriate action. (I’d also make it a GET and not a POST)
If you really can’t separate the functionality out into two views, then you can retrieve the value from those buttons if you use the same name attribute on those buttons. For example, if you set name="Submit" on both buttons, you would get the value of that button from request.POST['Submit'] (Note that it’s request.POST, not request.post.
Side note: There are no functional differences between a CBV and an FBV. Whatever you can do in one, you can do in the other. The differences are a matter of code structure and not of functionality.
Also, if you’re still learning about the CBVs, I suggest you become very familiar with the Classy Class-Based Views site along with the CBV diagrams page. The two of them are excellent resources for getting a real understanding of how CBVs are constructed and work.
Additionally, you have:
This is not valid, because you’ve defined it as:
Which defines FisherAgreement as a view and not a form.